ACP-610 Practice Questions

Jon needs Move Issues and Create Issues permissions to move an issue from project A to project B.

Move Issues permission allows him to initiate the move operation, while Create Issues permission

allows him to create the issue in the destination project. Transition Issues permission is not relevant

for moving issues, as it only affects workflow transitions. Administer Projects permission is not

required for moving issues, unless the issue type or workflow needs to be changed during the move.

Assign Issues permission is not required for moving issues, unless the assignee needs to be changed

during the move. Reference: [Moving an issue], [Managing Jira Projects Data Center and Server:

Certification Bundle]

The solution that meets this requirement is to update the board filter and add: AND (labels !=

daily.business OR labels IS EMPTY). This will exclude issues that have the label daily_business from

the board filter, which determines which issues are displayed on the board. It will also include issues

that have no labels at all, as some issues in your project may not have labels. The other solutions do

not meet this requirement, as they either do not exclude issues with daily_business label, or exclude

issues with no labels. Reference: Configuring filters, Advanced searching - operators reference

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. Reference: Configuring columns, Moving an issue

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. Reference: [Configuring card layout], [Configuring swimlanes], [Configuring card colours], [Using

boards]

One difference between Scrum and Kanban boards is that only Scrum boards support selecting an

estimation method. Estimation is a way of measuring how much work is required to complete an

issue or a sprint. Scrum boards allow you to choose between story points, original time estimate, or

issue count as estimation methods. Kanban boards do not have estimation methods, as they focus on

managing the flow of work rather than planning sprints. Reference: Configuring estimation and

tracking, Estimating an issue

:

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 Sprint Report is the best report to provide a single comprehensive list of issues that were

completed in the last sprint. A Sprint Report shows the scope, status, and completion date of each

sprint. It also displays a breakdown of the completed, incomplete, and added issues in the sprint.

The team can see the story points associated with each completed issue, as well as the issue type of

each completed issue. They can also see the description of each issue that has not been completed

by clicking on the issue key or summary. A Sprint Report also helps to track the team’s performance

and identify any scope changes during the sprint. Reference: Managing Jira Projects Data Center and

Server: Certification Bundle, [Sprint Report | Jira Software Cloud]

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. Reference: [Configuring swimlanes], [Using swimlanes]