Atlassian ACP-610 Practice Test - Questions Answers, Page 7

A project screen is a screen that is used to display or edit issue fields in a project. A project administrator can modify his project screen if it meets the following prerequisites:

The screen is not shared with other projects or issue types.

The screen does not use the default system fields.

The screen scheme and the issue type screen scheme are not shared with other projects or issue types. If these conditions are met, the project administrator can perform the following actions on his project screen:

Create a new tab

Rename a tab

Remove a tab

Add an existing field

Remove a field

Reorder fields The project administrator cannot create a new field, set a default value for a field, or make a field required. These actions require Jira administration permissions.Reference:: https://support.atlassian.com/jira-software-cloud/docs/configure-field-layouts-in-the-issue-view/ https://support.atlassian.com/jira-software-cloud/docs/what-are-issue-fields/

A custom field is a field that is not part of the default set of Jira system fields. Creating a new custom field requires Jira administration permissions, so Max cannot perform action 1. However, adding an existing custom field to a transition screen does not require Jira administration permissions, as long as the screen is not shared with other projects or issue types. Therefore, Max can perform action 2 if he has the ''Administer Projects'' permission and the screen meets the prerequisites for editing.Reference:: https://support.atlassian.com/jira-software-cloud/docs/what-are-custom-fields/ https://support.atlassian.com/jira-software-cloud/docs/configure-screens/

The only users who can definitely see the Scrum board and rank issues are the members of the Developers role with Jira Software application access. This is because the Browse Projects permission, which allows users to see the project and its issues, is granted to the Developers role, and the Schedule Issues permission, which allows users to rank issues on a Scrum board, is granted to any logged in user who has Jira Software application access. The other options are incorrect because they either do not have Jira Software application access, which is required for both permissions, or they do not belong to the Developers role, which is required for the Browse Projects permission. For more information on project permissions and roles, seeUnderstand project permissions and rolesandManage project permissions.Reference:Manage project permissions,Understand project permissions and roles

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.

The project role that Clare needs is Assigners. This is because the Assigners role has been granted two permissions that Clare needs: Browse Projects and Assign Issues. The Browse Projects permission allows Clare to see the project and its issues, and the Assign Issues permission allows Clare to re-assign issues to subject matter experts. The other roles do not have both of these permissions. For example, the Viewers role only has the Browse Projects permission, but not the Assign Issues permission. The Administrators role has both permissions, but also has other permissions that Clare does not need, such as Administer Projects and Delete Issues. The Assignables role only has the Assignable User permission, which allows users to be assigned issues, but not to assign issues to others. The Workers role only has the Work On Issues permission, which allows users to log work on issues, but not to assign issues to others. The Editors role only has the Edit Issues permission, which allows users to modify issue details, but not to assign issues to others. For more information on how project permissions and roles work, seeUnderstand project permissions and rolesandManage project permissions.Reference:Manage project permissions,Understand project permissions and roles

Bob needs security level access to see all the issues in the scrum project. Security levels are a way of restricting the visibility of certain issues within a project to specific users or groups. If Bob does not have the appropriate security level for some issues, he will not be able to see them. Browse Projects permission alone is not enough to see all the issues in a project that has security levels configured. Project permission, global permission, and board access are not related to issue visibility within a project.Reference:Configuring issue-level security,Managing Jira Projects Data Center and Server: Certification Bundle

A project administrator can remove watchers from project notifications, if they have the Manage Watchers permission. This is a task that does not require Jira administrator access, and can be done by the project administrator from the issue view. Removing a priority value used by the project, updating permissions for a project user, and limiting who can bulk edit project issues are all tasks that require Jira administrator access, and cannot be done by the project administrator.Reference:Managing watchers,Managing Jira Projects Data Center and Server: Certification Bundle

Savresh needs Assignable User permission.This permission determines which users can be assigned to issues in a project1. If Savresh does not have this permission, they will not be able to re-assign issues to themselves, even if they can create and assign issues to others.

Testers need Assign Issues permission.This permission determines which users can assign issues to other users or to themselves1. If the Testers group does not have this permission, they will not be able to re-assign issues to anyone, including Savresh.

Jira attachments are files that users can attach to issues to share information with their team. Users can search for issues that contain attachments by using theattachmentsfield in the advanced search. For example,attachments is not EMPTYwill return all issues that have at least one attachment. Therefore, option A is true.