ATLASSIAN ACP-610 - Managing Jira Projects for Data Center and Server Certification

 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

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. References: : 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/

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. References: Configuring estimation and tracking, Estimating an issue

The correct JQL query to find issues reported by either Paul or Tessa that are still unassigned is: Reporter IN (Paul, Tessa) AND Assignee IS EMPTY. This query uses the IN operator to specify a list of values for the Reporter field, and the IS EMPTY operator to check if the Assignee field has no value. The other options are incorrect because they use invalid syntax or operators, such as “-”, NULL, or Unassigned. For more information on JQL syntax and operators, see JQL operators and Use advanced search with Jira Query Language (JQL). References: JQL operators, Use advanced search with Jira Query Language (JQL)

The Cumulative Flow Diagram is the report that provides the information that the head of customer service wants. The Cumulative Flow Diagram is a tool that visualizes the quantity and distribution of work items along different stages of a process. The report shows how many work items are in each stage at any given time, and how they flow from one stage to another. The report can help identify potential bottlenecks in the support workflow by showing where work items accumulate or stagnate over time. For example, if the report shows a sudden increase or a wide band of work items in the “Waiting for Customer” stage, it may indicate that the customers are not responding quickly enough or that the support team is not following up effectively. The report can also help monitor the overall progress and performance of the support teams by showing the total number of work items created, resolved, and remaining over time. References: Managing Jira Projects Data Center and Server: Certification Bundle, Cumulative Flow Diagram

The correct JQL query to find all issues that were in the Closed status at some point in their lifecycle is: status WAS Closed. This query uses the WAS operator to check the previous values of the status field. The other options are incorrect because they either use invalid syntax, such as CHANGED FROM or -, or they do not capture all the issues that were ever closed, such as status = Closed or status CHANGED TO Open. For more information on JQL syntax and operators, see Advanced searching - operators reference and Advanced searching - fields reference. References: Advanced searching - operators reference, Advanced searching - fields reference

When you move an epic between projects that share an issue type scheme, all standard issues in the epic are moved along with it. This means that any issue type that is not a sub-task or an epic will be moved to the new project. Sub-task issues in the epic will not be moved unless their parent issues are also in the epic. Story issues in the epic will be moved only if they are standard issue types, not sub-tasks. Issues linked to the epic through issue links will not be moved as they are not part of the epic hierarchy. Therefore, the correct answer is A. References: Moving an issue, Working with epics

The board filter query that meets these requirements is (project = BERT AND type not in subTasklssueTypesO) OR (project = ERNIE AND issuetype Epic). This query will show all issue types from project BERT except sub-tasks, as well as only epics from project ERNIE. It will not show issues from any other projects, as it uses the OR operator to combine two conditions that specify the project names. The other queries do not meet all the requirements, as they either include sub-tasks from project BERT, exclude epics from project ERNIE, or show issues from other projects. References: Configuring filters, Advanced searching - fields reference

The team can use the Release link to remove issues as needed from the Done column. This will create a version in the project that contains all the issues that were removed, and the team can use the version report to see the details of each clean-up. Excluding issues in Done status from the board filter or via a sub-filter will not remove them from the Done column, but only hide them from view. Excluding issues where Resolution != EMPTY from the board filter will also hide issues from other columns that have a resolution set, which is not desired. References: [Releasing a version], [Managing Jira Projects Data Center and Server: Certification Bundle]