Susan has sent a first email to [email protected] which triggered the creation of the issue “LC-1” in the company-managed project “LC”.
Susan was mistakenly expecting an email notification from Jira acknowledging the fact that an issue was created from her email. Since she didn’t receive any notification email she took her first email and forwarded it to [email protected] again. Of course the second email didn’t have any reference to the issue key “LC-1”.
There are one email server and one mail handler configured with a the following type: “Create a new issue or add a comment to an existing issue”.
You are the admin for a large Jira Cloud instance used by thousands of active users and hundreds of agile teams.
A scrum master of one of these teams is worried about the numbers she is getting from Jira and told you that they may be a serious problem in Jira. In fact, she has executed three JQL queries (A), (B) and (C) and states that the number of issues returned from the query (A) must be equal to the sum of the number of issues returned from queries (B) and (C).
Here are the JQL queries:
(A) project = “DEV” → Number of issues: 1200
(B) project = “DEV” and fixVersion = 10 → Number of issues: 25
(C) project = “DEV” and fixVersion != 10 → Number of issues: 200
Your Software team is experimenting the use of Jira in their CI/CD tool chain and has raised the fact that they are not able to set the fix version field on all issues of their company-managed projects. Moreover, they are not able to easily fill user picker fields. Yet, they are able to create and edit all issues.
What additional configuration is needed while adhering to the “least privilege” principal? (choose two)
Rose has just created a Kanban team-managed project “MIG” with limited access.
Then Rose added users to the project and she mistakenly restricted the Story issue type visibility to the project role “Administrator”. Other than these changes, no project configuration has been updated.
After some days, users began complaining that they were not able to see Stories they create. So Rose needed to find a solution and decided to update the restriction of the issue type “Story” and added the project role “Viewer”.