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

Updating the name of your project will not affect the URL for issues, as they are based on the project key, not the name. The project key will also remain unchanged unless you explicitly change it. Issue search will still find issues from that project regardless of the name change. However, issue filters may need to be updated if they use the project name as a criterion. Therefore, the correct answer is C. References: Editing a project’s details, Changing the project key, Searching for issues using filters

 The Velocity Chart shows the amount of work completed by a team in each sprint. The green area represents the completed work, and the gray area represents the estimated work. The difference between the green and gray areas indicates a scope change, which means that issues were added or removed from the sprint after it started. In Combo Sprint 4, we can see that the green area is larger than the gray area, which means that more work was completed than estimated. This implies that some issues were added to the sprint after it started, or that some issues were re-estimated with higher values. Therefore, option C is correct. References: Velocity Chart, Managing Jira Projects Data Center and Server: Certification Bundle

Savresh needs Assignable User permission. This permission determines which users can be assigned to issues in a project1. If Savresh does not have this permission, they will not be able to re-assign issues to themselves, even if they can create and assign issues to others.

Testers need Assign Issues permission. This permission determines which users can assign issues to other users or to themselves1. If the Testers group does nothave this permission, they will not be able to re-assign issues to anyone, including Savresh.

To restore an issue from the project archive, Bethany needs two permissions: Restore Issues and Browse Project Archive. The Restore Issues permission allows Bethany to restore issues that have been archived in a project. The Browse Project Archive permission allows Bethany to view the archived issues in a project. Without these permissions, Bethany will not be able to access or restore the archived issue, even if she knows the URL. The other permissions are not relevant for restoring an issue. The Move Issues permission allows Bethany to move issues from one project to another. The Edit Issues permission allows Bethany to modify the details of an issue. The Browse Projects permission allows Bethany to see the project and its issues, but not the archived ones. For more information on how to archive and restore issues, see Archive and restore issues and Manage project permissions. References: Archive and restore issues, Manage project permissions

The Version Report and the Sprint Health Gadget are two gadgets that can show the information that the product owner needs. The Version Report shows the progress of a version by comparing the estimated amount of work to the completed work. The report also shows a projected release date based on the team’s average velocity. The product owner can use this report to monitor the overall progress of the next release and determine if it will ship on time. The Sprint Health Gadget shows a snapshot of key sprint information such as time elapsed, percentage of scope change, sprint goal, and team members’ availability. The product owner can use this gadget to see how each scrum team is performing in their current sprint and identify any issues or risks. References: Managing Jira Projects Data Center and Server: Certification Bundle, Version Report, Sprint Health Gadget

A project administrator can remove watchers from project notifications, if they have the Manage Watchers permission. This is a task that does not require Jira administrator access, and can be done by the project administrator from the issue view. Removing a priority value used by the project, updating permissions for a project user, and limiting who can bulk edit project issues are all tasks that require Jira administrator access, and cannot be done by the project administrator. References: Managing watchers, 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]

The statement that is definitely true is that bugs can be dragged from “In Progress” to “In Test” on this board. This is because the board configuration shown in the image has two columns: “In Progress” and “Done”. The “In Progress” column has three statuses mapped to it: “To Do”, “InProgress”, and “In Test”. The “Done” column has one status mapped to it: “Done”. Therefore, issues can be moved from one status to another within the same column by dragging them on the board. However, issues cannot be moved from one column to another by dragging them on the board, as this would require a workflow transition that is not available in a simplified workflow. A simplified workflow is a default workflow that allows any user with the Edit Issues permission to add or remove statuses on the fly. To move an issue from one column to another, you need to use the workflow button on the issue detail view and select a transition that matches the status of the destination column. References: Configuring columns, Using a simplified workflow