Free ACP-620 Exam Dumps Preview

Swimlanes are a way of grouping issues on a board based on certain criteria, such as assignee, priority, query, or epics. If you want to see a grouping of stories without epics, you can use a query swimlane with the condition epic is EMPTY, which will show only issues that are not part of any epic. The other options will either show epics or not group stories at all. Therefore, the correct answer is A.
References:
[Configuring swimlanes], [Advanced searching - fields reference]

Moving issues requires Move Issues permission in the source project and Create Issues permission in the destination project.

Each component in Jira can have its own default assignee, which overrides the project default. When an issue is created and includes that component, the component lead automatically becomes the assignee.

The epic completion date is hard to predict because the team adds new stories throughout the epic. This means that the scope of the epic is not fixed and can change over time. The Epic Report shows the progress of an epic by comparing the estimated amount of work to the completed work. The report also shows a projected completion date based on the team'saverage velocity. However, if the team keeps adding new stories to the epic, the estimated amount of work will increase and the projected completion date will be pushed further. This makes it difficult to plan and deliver the epic within a certain timeframe.
References:
Managing Jira Projects Data Center and Server: Certification Bundle, Epic Report

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]

The Pie Chart gadget visualizes issue counts or percentages by any chosen field, such as Priority, providing a quick overview of distribution.

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]

Based on the current configuration, the assignee field will show Mac Taylor after creating the test issue.
This is because the Macbook 13" component has Mac Taylor as the component lead and the component/s field has been configured to override the project's default assignee when using a certain component.
Therefore, when creating an issue with the Macbook 13" component, the assignee field will automatically be set to Mac Taylor, regardless of the default assignee of the project or the value of the assignee field before creating the issue

References:
What are components? | Jira Software Cloud | Atlassian Support
How to enable and edit component/s , affects Version/s and fix version ...

Automation rules with a scheduled trigger can query resolved issues and transition them to "Closed" after the desired period, ensuring consistent cleanup.

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 the attachments field in the advanced search. For example, attachments is not EMPTY will return all issues that have at least one attachment. Therefore, option A is true.

To perform the tasks that Jon needs, he requires three additional permissions: Close Issues, Transition Issues, and Schedule Issues. The Close Issues permission allows Jon to transition issues from the Resolved column to the Closed column on the Scrum board. The Transition Issues permission allows Jon to move issues through any workflow transition on the Scrum board. The Schedule Issues permission allows Jon to set or edit the Due Date of an issue. The other permissions are not additional or necessary for Jon's tasks. The Work On Issues permission allows Jon to log work on an issue, but not to set or edit the Due Date. The Browse Projects permission is already granted to Jon, since he can see the issues in the project. For more information on how to manage project permissions, see Manage project permissions and Understand project permissions and roles.
References:
Manage project permissions, Understand project permissions and roles

A possible reason why Sam can only see some of the issues on the project's Kanban board but sees all of them in the issue search is that the column mapping of the board does not include all the statuses of the different workflows used by the issue types. Column mapping determines which statuses are mapped to which columns on a board, and only issues with mapped statuses are displayed on the board. If an issue type has a workflow with a status that is not mapped to any column, then it will not appear on the board.
Board permissions, issue-level security, and workflow conditions do not affect the visibility of issues on a board, as they apply to both the board and the issue search. Therefore, the correct answer is B.
References:
[Configuring columns], [Configuring workflows]