ATLASSIAN ACP-610 Test Dumps

A.   Assigners

Answer DescriptionExplanation: 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.

B.   any logged in user

Answer DescriptionExplanation: 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.

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

Answer DescriptionExplanation: 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.

E.   3

Answer DescriptionExplanation: 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.

C.   Use the currentUser0JQL function in the filter.

Answer DescriptionExplanation: 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.

A.   card layout

Answer DescriptionExplanation: The best configuration to meet the team’s need of displaying keywords prominently when viewing all cards on a board is card layout. Card layout allows you to customize what fields are shown on each card on a board, and you can choose to show any custom field of type Labels on the cards. Swimlanes are used to group issues into horizontal lanes based on certain criteria, such as assignee, priority, or query, but they do not show labels on each card. Card colours are used to highlight issues based on certain attributes, such as issue type, priority, or query, but they do not show labels on each card either. Issue detail view is used to show more information about an issue when you select it on a board, but it does not affect how cards are displayed on the board. Therefore, the correct answer is A.

C.   The statuses are mapped to the same column.

Answer DescriptionExplanation: If Quang can transition issues from Resolved to Done using the workflow button on issues in his project, but cannot drag them from Resolved to Done on the project’s Kanban board, a possible reason is that the statuses are mapped to the same column. The columns on a Kanban board represent the stages of work in a project. Each column can have one or more statuses mapped to it. To move an issue from one column to another, you need to drag and drop it to a column that has a different status mapped to it. If the statuses are mapped to the same column, you cannot move the issue by dragging it on the board, but you can still use the workflow button to change its status.

B.   Expedite

Answer DescriptionExplanation: The issue will appear in the Expedite swimlane, because it matches the query priority = Blocker. Swimlanes are used to group issues on the board based on a common attribute, such as assignee, epic, or a custom query. The board’s swimlane configuration shows that the first swimlane is Expedite, which has the query priority = Blocker. This means that any issue with a blocker priority will be placed in this swimlane, regardless of its other attributes. The other swimlanes have different queries that do not match the issue’s attributes, such as type, labels, or reporter. Therefore, the issue will not appear in those swimlanes. The last swimlane is Everything Else, which is the default swimlane for any issue that does not match any of the previous queries. However, since the issue matches the Expedite query, it will not fall into this swimlane either. Hence, the correct answer is B.