Atlassian Managing Jira Projects for Data Center and Server Certification ACP-610 Exam Practice Test

Answer : E

The gadget that meets Kim's need is theIssue Statisticsgadget. 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:

TheHeat Mapgadget 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.

TheTwo Dimensional Filter Statisticsgadget 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.

TheFilter Resultsgadget 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.

TheIssues in Progressgadget 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.

Answer : A

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'', ''In Progress'', 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.Reference:Configuring columns, Using a simplified workflow

Answer : E

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

Answer : C

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.Reference: Viewing the Velocity Chart, Scope change

Answer : C

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.Reference:Editing a project's details,Changing the project key,Searching for issues using filters

Answer : C, D

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.Reference: Viewing the Velocity Chart, Scope change

Answer : B

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.Reference: [Configuring columns], [Configuring workflows]