Atlassian Atlassian Certifications ACP-610 Questions & Answers

• Question 71:

  A shareddashboard displays a gadget thatis based on a shared filter.

  Currently, each person who views the gadget sees counts of all the issues in a project by status.

  The team's requirement is that each person who views the gadget will see counts of only their assigned issues by status.

  What must you do in order to meet this requirement?

  A. Configure the 'Who can view this filter" setting.

  B. Reconfigure the dashboard viewers.

  C. Use the currentUser0JQL function in the filter.

  D. Replace it with the "Assigned to Me" gadget

  E. Modify the Assignable User permission.

  Correct Answer: C

  The best way to meet the team's requirement is to use the currentUser() JQL function in the filter. This function returns the current user who is viewing the gadget, and can be used to filter issues by assignee. For example, if the filter is "project = ABC and assignee = currentUser()", then each person who views the gadget will see counts of only their assigned issues by status.This way, you do not need to reconfigure the dashboard viewers or modify the Assignable User permission, which are global settings that affect all users. You also do not need to replace it with the "Assigned to Me" gadget, which does not show counts by status. Configuring the "Who can view this filter" setting does not affect the results of the filter, but only its visibility. References: Managing Jira Projects Data Center and Server: Certification Bundle, [Advanced searching - functions reference | Jira Software Cloud]

• Question 72:

  A Scrum project has the following five configured versions: Howmany of them will be available in the versions panel of the project backlog?

  

  A. 4

  B. 1

  C. 2

  D. 5

  E. 3

  Correct Answer: E

  Three versions will be available in the versions panel of the project backlog:

  epsilon, delta, and gamma. These are the three unreleased versions in the project, as shown in the image. The versions panel only shows unreleased versions, as they are used to plan and track the progress of upcoming releases. Released

  and archived versions are not shown in the versions panel, as they are considered completed and no longer relevant for planning purposes. References: [Working with versions], [Managing Jira Projects Data Center and Server: Certification

  Bundle]

• Question 73:

  Sam and Jo are product managers responsible for two separate products. Each product has its own Jira project and a corresponding Scrum board.

  Management requests an integration between the products. Sam and Jo decide to create all the integration-related issues in Sams project and label them integration".

  Jo updated his Scrum board's saved filter to include the relevant integration issues from Sam's project.

  Which statement is definitely true?

  A. All integration issues always appear on top of Jo's backlog.

  B. Changes to the rank of integration issues on Jo's board are reflected on Sam's board.

  C. Jo is unable to rank integration issues created by Sam.

  D. Sam is unable to transition integration issues that were ranked by Jo.

  E. Integration issues can only be ranked on Sam's board.

  Correct Answer: B

  The statement that is definitely true is that changes to the rank of integration issues on Jo's board are reflected on Sam's board. This is because ranking is a global attribute that affects how issues are ordered across projects and boards based on their relative priority. When Jo updates his Scrum board's saved filter to include integration issues from Sam's project, he can rank them along with his own issues on his board. These changes will also affect how these issues are ranked on Sam's board, as they share the same rank field value. The other statements are not necessarily true or false, as they depend on other factors such as permissions, workflow configurations, or board settings. Therefore, the correct answer is B. References: [Ranking an issue], [Configuring filters]

• Question 74:

  A Scrum board contains issues from a single project. An extract of the project's permission scheme is shown.

  

  Who can definitely see the Scrurn board and rank issues?

  A. any member of Developers role with Jira Software application access

  B. any logged in user

  C. member of both Developers role and Product Owner role

  D. any member of Developers role

  Correct Answer: B

  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, see Understand project permissions and roles and Manage project permissions. References: Manage project permissions, Understand project permissions and roles

• Question 75:

  The extract of a permission scheme for a project is shown below.

  

  Clare is joining your team and needs to:

  1.

  analyze incoming requests with her initials tagged to a label

  2.

  re-assign requests to subject matter experts

  Which project role does Clare need?

  A. Assigners

  B. Viewers

  C. Administrators

  D. Assignables

  E. Workers

  F. Editors

  Correct Answer: A

  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, see Understand project permissions and roles and Manage project permissions. References: Manage project permissions, Understand project permissions and roles