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

The only field that can definitely be set by all project team members is Labels. Labels are a system field that can be edited by any user who has the Edit Issues permission in the project, regardless of the screen configuration. The other fields may or may not be editable by the project team members, depending on how they are configured in the screen scheme, field configuration scheme, and permission scheme of the project. For example, Attachment requires both the Edit Issues permission and the Create Attachments permission, Assignee requires both the Edit Issues permission and the Assignable User permission, Fix Version/s requires both the Edit Issues permission and the Resolve Issues permission, and Issue Type requires both the Edit Issues permission and a compatible issue type scheme. For more information on how to configure fields in Jira, see  Configuring fields and screens .  References:   Configuring fields and screens

Savresh needs Assignable User permission.  This permission determines which users can be assigned to issues in a project 1 . 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 themselves 1 . If the Testers group does not have this permission, they will not be able to re-assign issues to anyone, including Savresh.

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]

A custom field is a field that is not part of the default set of Jira system fields. Creating a new custom field requires Jira administration permissions, so Max cannot perform action 1. However, adding an existing custom field to a transition screen does not require Jira administration permissions, as long as the screen is not shared with other projects or issue types. Therefore, Max can perform action 2 if he has the “Administer Projects” permission and the screen meets the prerequisites for editing.  References:  : https://support.atlassian.com/jira-software-cloud/docs/what-are-custom-fields/ https://support.atlassian.com/jira-software-cloud/docs/configure-screens/

Jira administrators can create and update global priorities, which are the default set of priorities available in each project. Project administrators cannot re-order, create, or update priorities in their projects, unless they have Jira administrator access. The same set of priorities is not always available in each project, as Jira administrators can configure priority schemes to assign different priorities to different projects.  References:  [Configuring priorities], [Managing Jira Projects Data Center and Server: Certification Bundle]

The “Task management” project template is designed for managing simple tasks and tracking progress. By default, this template enables ranking of standard issue types, which allows you to order issues by priority on a board. The other features mentioned in the options are not enabled by default in this template. Therefore, the correct answer is B.  References :  Creating a project ,  Ranking an issue

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]

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