Free Practice Questions for ATLASSIAN ACP-610 Exam

The gadget that meets Kim’s need is the Issue Statistics gadget. This gadget displays the collection of issues returned from a filter, broken down by a field. Kim can configure the gadget to use her project as the filter, and the issue type as the field. The gadget will then show the following information for issues in her project:

the total count of all issues

the total count of each issue type

the distribution of each issue type as a percentage

a graphical chart display of that percentage

The other gadgets are not suitable because:

The Heat Map gadget displays issues from a project or filter, grouped by a statistic type, in a heat map format. Issues can be grouped by any statistic type (e.g. Status, Priority, Assignee, etc). However, this gadget does not show the total count of all issues, nor the distribution of each issue type as a percentage.

The Two Dimensional Filter Statistics gadget displays issues from a filter in a table format, where each cell shows the number of issues for a given combination of two statistics types (e.g. Status vs Priority, Assignee vs Issue Type, etc). This gadget does not show the total count of all issues, nor a graphical chart display of that percentage.

The Filter Results gadget displays the results of an issue filter on the dashboard. This gadget does not show any summary or breakdown of the issues by any field, nor a graphical chart display of that percentage.

The Issues in Progress gadget displays all issues that are in progress and assigned to the user viewing the dashboard. This gadget does not show any information about other issues or issue types in the project, nor a graphical chart display of that percentage.

References: Use dashboard gadgets, Gadgets for Jira applications

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 reason why you are unable to drag an issue into a future sprint in the backlog is that ranking is disabled. Ranking is a feature that allows you to order issues based on their relative priority or importance. Ranking is enabled by adding “ORDER BY Rank ASC” or “ORDER BY Rank DESC” to your board filter query. Ranking is required for Scrum boards, as it determines the order of issues in your backlog and sprints. If ranking is disabled, you cannot drag and drop issues in your backlog or plan future sprints. References: Ranking an issue, Configuring filters

The solution that will meet the team’s requirements of using agile boards with minimal disruption to their current configuration is to use a Kanban board for tasks and a Scrum board for features in the current project. This way, they can use different agile methodologies for different issue types without creating a new project or changing their existing configuration. They can use a Kanban board for tasks to handle them based on priority and rank and release them incrementally as needed. They can use a Scrum board for features to develop them during three week iterations with sprints and backlogs. The other solutions are either not feasible or not optimal for their needs. Therefore, the correct answer is E. References: [Creating a board], [Using a Scrum board], [Using a Kanban board]

https://support.atlassian.com/jira-software-cloud/docs/understand-project-permissions-and-roles/

The two permissions that can be granted through a project role are:

A. see issues with a security level

C. share a dashboard with other auditors

These permissions are related to the project level and can be configured by the project administrator using the permission scheme or the dashboard settings.According to the documentation1, a project role can be granted the following permissions:

Browse Projects: View the project and its issues.

Create Issues: Create new issues.

Edit Issues: Edit existing issues.

Schedule Issues: Edit the Due Date of an issue, or rank issues on a Scrum board.

Move Issues: Move issues from one project to another, or change the issue type.

Assignable User: Be assigned issues.

Assign Issues: Assign issues to other users.

Resolve Issues: Resolve or reopen issues, or set a resolution when closing issues.

Close Issues: Close issues.

Modify Reporter: Modify the Reporter field of an issue.

Delete Issues: Delete issues from the project.

Link Issues: Link issues to each other, or create sub-tasks under an issue.

Set Issue Security: Set a security level on an issue to control who can see it.

View Voters and Watchers: View the list of voters and watchers for an issue.

Manage Watchers: Add or remove watchers for an issue.

View Read-Only Workflow: View the workflow diagram for an issue, but not edit it.

Manage Sprints: Start, complete, or edit sprints on a Scrum board.

Additionally, a project role can be given access to share a dashboard with other users or groups2. To do this, the project administrator needs to:

Go to Dashboards > View all dashboards

Find the dashboard to share and click > Share

Click Edit permissions

Under Add Permissions, select Group or Project Role

Choose the auditors project role from the dropdown menu

Click Add

The other options are not correct because:

B. see issues that have been archived is not a permission that can be granted through a project role.Archived issues are hidden from all users except Jira administrators3. To view archived issues, the auditors would need to have the Administer Jira global permission, which is not related to project roles.

D. subscribe other auditors to a search result is not a permission that can be granted through a project role.Subscribing other users to a search result is a feature that requires the Manage Group Filter Subscriptions global permission4. This permission is not related to project roles and can only be granted by Jira administrators to individual users or groups.

E. use bulk change to update seven issues is not a permission that can be granted through a project role.Bulk change is an operation that requires the Bulk Change global permission5. This permission is not related to project roles and can only be granted by Jira administrators to individual users or groups.

The reason why your team completed more story points than they committed in their last sprint is that someone increased the story point value on an issue mid-sprint. This will increase the total story points completed at the end of the sprint, but not affect the total story points committed at the start of the sprint. Therefore, it will result in a positive scope change. The other reasons mentioned in the question do not explain why your team completed more story points than they committed, as they either do not affect story points at all, or affect both committed and completed story points equally. References: Viewing the Velocity Chart, Scope change

Epics are moved automatically but epic links are lost when stories are moved to another project using a bulk operation. This is because epics are a type of issue, and issues can be moved across projects. However, epic links are a type of issue link, and issue links cannot be moved across projects. Therefore, the stories will lose their epic links after the move, and the epics will remain in the original project. References: [Moving multiple issues], [Managing Jira Projects Data Center and Server: Certification Bundle]