Question 65 - ACP-610 discussion

https://support.atlassian.com/jira-software-cloud/docs/understand-project-permissions-and-roles/

The two permissions that can be granted through a project role are:

A) see issues with a security level

C) share a dashboard with other auditors

These permissions are related to the project level and can be configured by the project administrator using the permission scheme or the dashboard settings. According to the documentation1, a project role can be granted the following permissions:

Browse Projects: View the project and its issues.

Create Issues: Create new issues.

Edit Issues: Edit existing issues.

Schedule Issues: Edit the Due Date of an issue, or rank issues on a Scrum board.

Move Issues: Move issues from one project to another, or change the issue type.

Assignable User: Be assigned issues.

Assign Issues: Assign issues to other users.

Resolve Issues: Resolve or reopen issues, or set a resolution when closing issues.

Close Issues: Close issues.

Modify Reporter: Modify the Reporter field of an issue.

Delete Issues: Delete issues from the project.

Link Issues: Link issues to each other, or create sub-tasks under an issue.

Set Issue Security: Set a security level on an issue to control who can see it.

View Voters and Watchers: View the list of voters and watchers for an issue.

Manage Watchers: Add or remove watchers for an issue.

View Read-Only Workflow: View the workflow diagram for an issue, but not edit it.

Manage Sprints: Start, complete, or edit sprints on a Scrum board.

Additionally, a project role can be given access to share a dashboard with other users or groups2. To do this, the project administrator needs to:

Go to Dashboards > View all dashboards

Find the dashboard to share and click > Share

Click Edit permissions

Under Add Permissions, select Group or Project Role

Choose the auditors project role from the dropdown menu

Click Add

The other options are not correct because:

B) see issues that have been archived is not a permission that can be granted through a project role. Archived issues are hidden from all users except Jira administrators3. To view archived issues, the auditors would need to have the Administer Jira global permission, which is not related to project roles.

D) subscribe other auditors to a search result is not a permission that can be granted through a project role. Subscribing other users to a search result is a feature that requires the Manage Group Filter Subscriptions global permission4. This permission is not related to project roles and can only be granted by Jira administrators to individual users or groups.

E) use bulk change to update seven issues is not a permission that can be granted through a project role. Bulk change is an operation that requires the Bulk Change global permission5. This permission is not related to project roles and can only be granted by Jira administrators to individual users or groups.