Pass the ATLASSIAN Jira Project Administrator ACP-610 Questions and answers with CertsForce

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 Sprint Report is the best report to provide a list of all issues included in a particular 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 release manager can easily view the list of incomplete issues in the Issue Navigator by clicking on the View in Issue Navigator link at the bottom of the report. A Sprint Report also helps to track the team’s performance and identify any scope changes during the sprint. References: Managing Jira Projects Data Center and Server: Certification Bundle, [Sprint Report | Jira Software Cloud]

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 two actions that are reflected as scope change are dragging an estimated story from the backlog to the sprint and modifying the estimate value on a committed story. Scope change is a measure of how much work was added or removed from a sprint after it started. It is calculated by comparing the total story points committed at the start of the sprint and the total story points completed at the end of the sprint. If you add or remove issues from a sprint, or change their estimates, you are changing the scope of the sprint. The other actions mentioned in the question do not affect the scope of the sprint, as they do not change the amount of work planned or done in the sprint. References: Viewing the Velocity Chart, Scope change

 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 issue34 References:

3: What are components? | Jira Software Cloud | Atlassian Support

4: How to enable and edit component/s , affects Version/s and fix version …

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]

The only field that can definitely be set by all project team members is Labels. Labels are a system field that can be edited by any user who has the Edit Issues permission in the project, regardless of the screen configuration. The other fields may or may not be editable by the project team members, depending on how they are configured in the screen scheme, field configuration scheme, and permission scheme of the project. For example, Attachment requires both the Edit Issues permission and the Create Attachments permission, Assignee requires both the Edit Issues permission and the Assignable User permission, Fix Version/s requires both the Edit Issues permission and the Resolve Issues permission, and Issue Type requires both the Edit Issues permission and a compatible issue type scheme. For more information on how toconfigure fields in Jira, see Configuring fields and screens. References: Configuring fields and screens

Jira administrators can create and update global priorities, which are the default set of priorities available in each project. Project administrators cannot re-order, create, or update priorities in their projects, unless they have Jira administrator access. The same set of priorities is not always available in each project, as Jira administrators can configure priority schemes to assign different priorities to different projects. References: [Configuring priorities], [Managing Jira Projects Data Center and Server: Certification Bundle]

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. References: [Moving an issue], [Managing Jira Projects Data Center and Server: Certification Bundle]

If you manage a Scrum project with two development teams and want to provide each team with an individual Burndown Chart, you can create two Scrum boards using the Team field in their board filters. A Burndown Chart is a report that shows the amount of work remaining in a sprint, based on the issues that are included in the board filter. By using the Team field in the board filter, you can ensure that each board only shows the issues that belong to a specific team, and thus generate a separate Burndown Chart for each team. The other options will either show a combined Burndown Chart for both teams or not use the Team field at all. Therefore, the correct answer is D. References: [Creating a board], [Configuring filters], [Viewing the Burndown Chart]