Managing Jira Projects for Cloud

The Cumulative Flow Diagram is the report that provides the needed insight to see if frequent scope change mid-sprint is causing bottlenecks. The Cumulative Flow Diagram shows the quantity and distribution of work items along different stages of a process over time. The report can help identify potential bottlenecks in the 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 "In Progress" stage, it may indicate that the team is overloaded with work or facing some blockers. If the team often accepts new requests from outside groups during an active sprint, the report can show how this affects the flow of work and the completion of the sprint goal.

References:
Managing Jira Projects Data Center and Server: Certification Bundle, Cumulative Flow
Diagram

The statusCategoryChangedDate field tracks when an issue last changed status. Using JQL with a date comparison highlights stale work items.

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

Sub-tasks are a type of issue that can be used to break down a parent issue into smaller and more manageable pieces. Sub-tasks can be displayed as cards in the Active sprints view of a Scrum board, which allows you to track their progress and status. However, sub-task estimations are not rolled up and displayed on the parent card, as they use a different field than the parent issue. Sub-tasks can be created by anyone who has the Create Issue permission in the project, not only by board administrators. Sub-tasks cannot be displayed as cards in the Backlog view, as they are only visible under their parent issues. Sub-tasks will not automatically get resolved when the parent is moved to the Done column, as they have their own workflow transitions and conditions. Therefore, the correct answer is C.
References:
[Working with sub-tasks], [Configuring columns]

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

A Kanban board is the best option for Gen to prioritize and triage support requests using drag-and-drop. A Kanban board allows Gen to quickly assign issues to herself or other team members by dragging them to the appropriate column. She can also transition issues to In Progress by moving them across the workflow.
Additionally, she can instantly associate issues with Epics by dragging them to the Epic panel on the right side of the board. A Kanban board also provides a visual overview of the current status and progress of the support requests.
References:
Managing Jira Projects Data Center and Server: Certification Bundle, Configuring projects | Administering Jira applications Data Center and ..., [Working with issues | Jira
Software Cloud]

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:

1. the total count of all issues 2. the total count of each issue type
3. the distribution of each issue type as a percentage 4. a graphical chart display of that percentage

The other gadgets are not suitable because:

1. 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.
2. 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.
3. 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.
4. 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 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:

1. The screen is not shared with other projects or issue types.
2. 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:

1. Create a new tab
2. Rename a tab

3. Remove a tab
4. Add an existing field
5. Remove a field
6. 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/

The statement that is definitely true is that changes to the rank of integration issues on Jo's board are reflected on Sam's board. This is because ranking is a global attribute that affects how issues are ordered across projects and boards based on their relative priority. When Jo updates his Scrum board's saved filter to include integration issues from Sam's project, he can rank them along with his own issues on his board.
These changes will also affect how these issues are ranked on Sam's board, as they share the same rank field value. The other statements are not necessarily true or false, as they depend on other factors such as permissions, workflow configurations, or board settings. Therefore, the correct answer is B.
References:
[Ranking an issue], [Configuring filters]

When a project is created with a shared configuration, it inherits the configurations of an existing project.
This includes the workflow, issue types, screens, fields, permissions, notifications, and schemes associated with them. However, the component lead assignments and versions are specific to each project and are not shared. Therefore, the correct answer is C and E.
References:
Creating a project, Configuring projects