When using a bulk move operation to migrate issues between issue types within a company-managed project, certain elements may need to change due to differences in configurations (e.g., workflows, field configurations) associated with the source and target issue types. The two elements that might need to change are statuses (Option A) and required fields (Option C).

Explanation of the Correct Answers :

Statuses (Option A) :

Each issue type in a company-managed project can be associated with a different workflow via the project’s workflow scheme . If the source and target issue types use different workflows, the statuses available in the target workflow may differ from those in the source workflow. During a bulk move, you must map the current status of each issue to a valid status in the target workflow, as the issue’s status might not exist in the new workflow.

Exact Extract from Documentation :

Move issues in Jira Cloud

When moving issues to a different issue type in a company-managed project, you may need to map statuses if the source and target issue types use different workflows.

To move issues:

Select issues and choose Bulk change > Move issues .

Choose the target issue type.

Map statuses from the source workflow to the target workflow if they differ. Note : Status mapping is required when workflows have different statuses. (Source: Atlassian Support Documentation, "Move issues in Jira Cloud")

Why This Fits : If the target issue type’s workflow has different statuses, the issues’ statuses must be mapped during the move, making statuses a potential element that needs to change.

Required fields (Option C) :

Different issue types can be associated with different field configuration schemes , which define whether fields are required, optional, or hidden. If the target issue type requires fields that were not required for the source issue type (e.g., a custom field or system field like Due Date ), you must provide values for these required fields during the bulk move operation.

Exact Extract from Documentation :

Bulk move issues

When moving issues to a different issue type, you may need to update fields if the target issue type’s field configuration requires fields that were not required for the source issue type.

During the move:

The bulk move wizard prompts you to provide values for any newly required fields.

Ensure all required fields have valid values to complete the move. Note : Field configurations are defined in Settings > Issues > Field configurations . (Source: Atlassian Support Documentation, "Move issues in Jira Cloud")

Why This Fits : Required fields may differ between issue types due to field configuration schemes, and the bulk move operation will prompt for values if the target issue type has additional required fields, making required fields a potential element that needs to change.

Why Other Options Are Incorrect :

Priorities (Option B) :

The priority field is not typically tied to issue type-specific configurations (e.g., workflows or field configurations). Priorities are managed globally ( Settings > Issues > Priorities ) and are generally consistent across issue types unless restricted by a custom field configuration or workflow property, which is rare. A bulk move does not require changing priorities unless explicitly prompted by a field configuration, which is covered by required fields (Option C).

Extract from Documentation :

Priorities are global and not issue type-specific. They are only updated during a move if required by the target issue type’s field configuration.

(Source: Atlassian Support Documentation, "Manage priorities in Jira Cloud")

Resolutions (Option D) :

The resolution field is set or cleared based on workflow transitions (e.g., resolving or reopening an issue). Moving issues between issue types within the same project does not inherently require changing the resolution, as it is tied to the issue’s status and workflow, not the issue type itself. Any status mapping (covered by Option A) handles resolution indirectly.

Extract from Documentation :

Resolution is managed by workflow transitions, not issue type changes. Moving issues does not typically require updating resolution unless a specific transition is involved.

(Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Labels (Option E) :

The labels field is a standard field that is not issue type-specific and does not typically require changes during a move unless it is a required field in the target issue type’s field configuration (covered by Option C). Labels are preserved during a move unless explicitly modified.

Extract from Documentation :

Fields like Labels are preserved during a move unless the target issue type’s field configuration requires a new value.

(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")

Additional Notes :

The bulk move operation is performed via Issues > Search for issues > Bulk change > Move issues , requiring the Move Issues permission.

The need to change statuses and required fields depends on the differences in workflows and field configurations between the source and target issue types.

If the issue types share the same workflow and field configuration, no changes may be needed, but the question asks for elements that might need to change.

Christian’s saved filter shows bugs that have not been updated in the past two weeks, likely using a JQL query like issuetype = Bug AND updated < = -2w. Running a bulk operation to change the priority to Highest on all issues in the filter will update the issues, affecting their updated timestamp. The definite outcome is that the saved filter will display no issues (Option A), as the issues will no longer meet the filter’s criteria after being updated.

Explanation of the Correct Answer (Option A) :

The saved filter likely uses a JQL query such as issuetype = Bug AND updated < = -2w, which returns bugs not updated in the past two weeks (i.e., updated timestamp is older than two weeks). When Christian performs a bulk operation to change the priority to Highest , each issue’s updated timestamp is set to the current time, as any edit (including priority changes) updates this field. After the operation, all issues in the filter will have a recent updated timestamp (e.g., within the last few minutes), causing them to no longer satisfy the updated < = -2w condition. As a result, the filter will return no issues.

Exact Extract from Documentation :

Bulk change issues

Bulk operations (e.g., changing priority) update issue fields and metadata, including the updated timestamp.

Impact on filters :

If a filter uses a condition like updated < = -2w, updating issues will change their updated timestamp, potentially excluding them from the filter. To perform a bulk change:

Run a filter in Issues > Search for issues .

Select Bulk change and choose an action (e.g., Edit Issues).

Update fields (e.g., Priority to Highest). Note : Bulk changes trigger the Issue Updated event, updating the updated field. (Source: Atlassian Support Documentation, "Bulk change issues in Jira Cloud")

Why This Fits : The bulk operation updates the updated timestamp of all issues, causing them to no longer meet the filter’s updated < = -2w condition, resulting in the filter displaying no issues, making Option A the definite outcome.

Why Other Options Are Incorrect :

Filter subscriptions based on the filter will stop sending emails (Option B) :

Filter subscriptions send emails based on the filter’s results and schedule (e.g., daily, weekly). The bulk operation does not disable the subscription or change its configuration; it only affects the filter’s results. If the filter returns no issues after the operation, the subscription will send an email with no results, but it will not stop sending emails entirely.

Extract from Documentation :

Filter subscriptions send emails based on the filter’s results and schedule. Empty results do not stop the subscription; they result in an empty email.

(Source: Atlassian Support Documentation, "Manage filters in Jira Cloud")

Christian will be added as a watcher on all the edited issues (Option C) :

Adding a watcher during a bulk operation is not automatic. Users are not added as watchers unless explicitly included in the bulk operation (e.g., via an Add Watcher action, which is not part of changing priority). Christian’s user settings or automation rules could theoretically add him as a watcher, but this is not a definite outcome of the priority change.

Extract from Documentation :

Bulk operations do not automatically add the user as a watcher. Use the Add Watcher action in a bulk operation to add watchers explicitly.

(Source: Atlassian Support Documentation, "Bulk change issues in Jira Cloud")

Email notifications will be sent during the bulk operation (Option D) :

Email notifications for the Issue Updated event (triggered by the priority change) depend on the project’s notification scheme and the recipients configured for the event (e.g., watchers, assignee). Notifications are not guaranteed, as they may be disabled or limited to specific users. Thus, this is not a definite outcome.

Extract from Documentation :

Bulk operations trigger the Issue Updated event, but notifications depend on the notification scheme and may not be sent if not configured.

(Source: Atlassian Support Documentation, "Configure notification schemes")

Additional Notes :

The bulk operation requires Christian to have the Edit Issues permission for the issues in the filter.

The filter’s JQL query (e.g., issuetype = Bug AND updated < = -2w) can be verified in Issues > Manage filters .

To avoid impacting the filter, Christian could modify the JQL to exclude recently updated issues or create a temporary filter for the bulk operation.

The inability to choose the Delete Issues bulk action on the Bulk Operation screen indicates that Taylor lacks the necessary permission to delete issues in the project. The Delete Issues permission, which is a project-level permission defined in the project’s permission scheme, is required for this action. Therefore, Taylor definitely needs project permissions (Option D).

Explanation of the Correct Answer (Option D) :

The Delete Issues permission allows users to delete issues, including via bulk operations. This permission is granted through the project’s permission scheme and is specific to the project containing the issues. If Taylor cannot select the Delete Issues bulk action, she lacks this permission for the project.

Exact Extract from Documentation :

Delete Issues permission

The Delete Issues permission allows users to delete issues, either individually or via bulk operations. This permission is granted via the project’s permission scheme.

To perform bulk operations:

Run a filter to select issues.

On the Bulk Operation screen, choose an action (e.g., Delete Issues). Note : Users must have the relevant permission (e.g., Delete Issues ) for all selected issues to see the action in the bulk operation wizard. To check permissions:

Go to Project settings > Permissions .

Verify which users, groups, or roles have the Delete Issues permission. (Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Why This Fits : The Delete Issues permission is a project-level permission, and granting it to Taylor will enable her to choose the Delete Issues bulk action, making project permissions (Option D) the correct answer.

Why Other Options Are Incorrect :

Organization admin privileges (Option A) :

Organization admins manage Atlassian organization settings, such as user access and billing. They do not directly control project-level permissions like Delete Issues .

Extract from Documentation :

Organization admins manage user access and organization settings. Project-specific actions, like deleting issues, are controlled by project permissions.

(Source: Atlassian Support Documentation, "Manage your Atlassian organization")

Jira administration privileges (Option B) :

Jira administrators manage global settings, such as schemes and user management. While they can modify permission schemes, the Delete Issues permission is project-specific and does not require Jira admin privileges to grant or use.

Extract from Documentation :

Jira administrators can modify permission schemes, but the Delete Issues permission is applied at the project level and does not require admin privileges to use.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Global permissions (Option C) :

Global permissions (e.g., Administer Jira , Create Projects ) control system-wide actions, not project-specific actions like deleting issues. The Delete Issues permission is project-level, not global.

Extract from Documentation :

Global permissions control system-wide actions, such as administering Jira or sharing filters. Project permissions, like Delete Issues , are specific to projects.

(Source: Atlassian Support Documentation, "Manage global permissions")

Project administration privileges (Option E) :

Project administration privileges (via the Administer Projects permission) allow users to manage project settings, such as components and permission schemes. However, deleting issues is an issue-level action that requires the Delete Issues permission, not administrative privileges.

Extract from Documentation :

The Administer Projects permission allows managing project settings. Deleting issues requires the Delete Issues permission, which is separate.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Additional Notes :

To resolve the issue, check Taylor’s permissions in Project settings > Permissions and ensure she has the Delete Issues permission, either directly, via a group, or via a project role.

If the issues in the bulk operation span multiple projects, Taylor needs the Delete Issues permission for all relevant projects.

The scenario indicates that Gary is no longer receiving notifications for issues he is watching, despite the notification scheme being correctly configured to notify watchers. This suggests that Gary has modified a personal setting that controls whether he receives notifications for watched issues. Based on Jira Software Cloud documentation, the relevant personal setting is "Notifications for relevant issues" (Option D).

Explanation of the Correct Answer (Option D):

In Jira Cloud, users can control their notification preferences through their personal settings in the user profile. The setting "Notifications for relevant issues" determines whether a user receives email notifications for events they are associated with, such as being a watcher of an issue.

If Gary disabled this setting (i.e., turned off notifications for relevant issues), he would stop receiving notifications for issues he is watching, even if the project’s notification scheme is configured to notify watchers.

Exact Extract from Documentation:

Manage your Jira notification emails

You can choose whether you want to receive email notifications about activity in your Jira products. For example, you can choose to receive emails when you’re added as a watcher to an issue, or when an issue you’re working on is updated.

To manage your notification preferences:

From your Jira site, select your profile picture in the top right and select Personal settings.

Under Email notifications, select whether you’d like to receive notifications for relevant issue activity.

On: Receive emails for issue activity you’re associated with, like when you’re a watcher, assignee, or reporter.

Off: Don’t receive emails for issue activity, even if you’re associated with the issue.

Note: This setting doesn’t affect emails about your account, like password resets. To manage those, update your Atlassian account preferences.

(Source: Atlassian Support Documentation, "Manage your Jira notification emails")

Why This Fits: The documentation explicitly states that turning off the "Notifications for relevant issues" setting prevents a user from receiving emails for issue activity they are associated with, including as a watcher. Since Gary is no longer receiving notifications for watched issues, this is the most likely setting he updated.

Why Other Options Are Incorrect:

Watch your issues (Option A):

This option refers to a setting that automatically adds a user as a watcher to issues they create or are assigned to. However, the question states that Gary is already watching the issues (since he was receiving notifications previously), so this setting is not relevant. Disabling this setting would only prevent Gary from being automatically added as a watcher to new issues, not stop notifications for issues he is already watching.

Extract from Documentation:

Watching issues

You can watch an issue to receive email notifications whenever it’s updated. By default, you may automatically watch issues you create or are assigned to, depending on your notification settings.

To change your auto-watch settings:

Select your profile picture and then select Settings.

Under Jira settings, select whether to automatically watch issues you create or are assigned to.

(Source: Atlassian Support Documentation, "Watch issues and manage your watchlist")

You make changes to the issue (Option B):

This option is not a standard personal setting in Jira Cloud. There is no user-level setting that specifically toggles notifications based on whether the user themselves makes changes to an issue. Notifications are controlled by the notification scheme and the user’s email notification preferences, not by a setting tied to the user’s own changes.

Email notifications format (Option C):

This setting allows users to choose the format of email notifications (e.g., HTML or text). Changing this setting affects how notifications are displayed, not whether they are sent. Therefore, it would not cause Gary to stop receiving notifications entirely.

Extract from Documentation:

Email format

You can choose whether notifications are sent in HTML or text format. This is managed in your Atlassian account settings, under email preferences.

(Source: Atlassian Support Documentation, "Manage your Atlassian account")

Additional Notes:

The question specifies that the notification scheme is correctly configured to notify watchers, so the issue lies with Gary’s personal settings, not the project or system configuration.

The "Notifications for relevant issues" setting is a global toggle that affects all notifications for issue activity a user is associated with, making it the most direct cause of Gary’s issue.

The time tracking feature in Jira Cloud allows logging work, tracking estimates, and managing time-related settings. The configuration that can be controlled globally across all projects is the default tracking time unit, unless users explicitly specify one (Option C), as this is set in the global time tracking settings.

Explanation of the Correct Answer (Option C) :

The default tracking time unit (e.g., hours, days) is configured globally in Jira Cloud’s time tracking settings and applies to all projects unless users specify a different unit when logging time or setting estimates. This setting determines how time is displayed and entered by default across the system.

Exact Extract from Documentation :

Configure time tracking in Jira Cloud

Global time tracking settings apply to all projects and include:

Default time unit : Sets the default unit for time tracking (e.g., hours, days). To configure:

Go to Settings > Issues > Time tracking .

Set the Default unit for time tracking (e.g., Hour). Impact : The default unit is used across all projects unless users explicitly specify another unit (e.g., 2d for days). Note : Requires Jira administrator permissions. (Source: Atlassian Support Documentation, "Configure time tracking in Jira Cloud")

Why This Fits : The default tracking time unit is a global setting that applies to all projects, making Option C the correct answer.

Why Other Options Are Incorrect :

The ability to log work on issues for specific groups (Option A) :

The ability to log work is controlled by the Work On Issues permission in each project’s permission scheme, not globally. Permissions are project-specific, even if projects share a scheme, and cannot be set globally for specific groups across all projects.

Extract from Documentation :

The Work On Issues permission is set in project permission schemes, not globally.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

The ability to edit or delete their own or other users’ worklogs for specific users (Option B) :

Permissions to edit or delete worklogs (e.g., Edit Own Worklogs , Edit All Worklogs , Delete Own Worklogs , Delete All Worklogs ) are also set in project permission schemes, not globally. These are project-specific settings.

Extract from Documentation :

Worklog permissions ( Edit Own Worklogs , Delete All Worklogs ) are configured in project permission schemes, not globally.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

The availability of time tracking fields on standard versus sub-task issue types (Option D) :

The availability of time tracking fields (e.g., Original Estimate, Remaining Estimate) is controlled by field configurations or screens , which are project-specific or issue type-specific. There is no global setting to differentiate time tracking fields between standard and sub-task issue types.

Extract from Documentation :

Time tracking fields are managed by field configurations and screens, not global settings. Their availability depends on project or issue type configurations.

(Source: Atlassian Support Documentation, "Configure field settings")

The requirement of an original estimate when creating issues (Option E) :

Requiring an Original Estimate is controlled by field configurations (making the field required) or workflow validators (enforcing a value during transitions). These are project-specific or issue type-specific, not global settings.

Extract from Documentation :

Requiring fields like Original Estimate is set in field configurations or workflow validators, not globally.

(Source: Atlassian Support Documentation, "Configure field settings")

Additional Notes :

Configuring global time tracking settings requires Jira administrator privileges and is done in Settings > Issues > Time tracking .

Other global time tracking settings include the format (e.g., hours per day, days per week) and whether time tracking is enabled.

Project-specific settings (e.g., permissions, field requirements) override global defaults for specific use cases.

To meet the requirements for the Attribute custom field’s behavior (hidden for Epics, optional for Stories, required for Bugs) in a company-managed project, you need to configure field configurations (Option A). Field configurations define whether a field is required, optional, or hidden for specific issue types.

Explanation of the Correct Answer (Option A) :

Field configurations control the behavior of fields (e.g., required, optional, hidden) for different issue types in a company-managed project. To meet the requirements:

For Epics , set the Attribute field to Hidden .

For Stories , set the Attribute field to Optional (not required).

For Bugs , set the Attribute field to Required .

This is achieved by creating multiple field configurations (one for each issue type’s behavior) and associating them with a field configuration scheme that maps configurations to issue types.

Exact Extract from Documentation :

Configure field settings

Field configurations define whether fields are required, optional, or hidden for specific issue types. A field configuration scheme maps field configurations to issue types in a project.

To configure:

Go to Settings > Issues > Field configurations .

Create or edit field configurations (e.g., one for Epics, Stories, Bugs).

For each configuration:

Mark a field as Required to enforce a value.

Mark a field as Hidden to remove it from screens.

Leave a field as Optional (default) if not required.

Create a field configuration scheme ( Settings > Issues > Field configuration schemes ) and map configurations to issue types.

Assign the scheme to the project in Project settings > Fields . Example : Hide a field for Epics, make it optional for Stories, and required for Bugs. (Source: Atlassian Support Documentation, "Configure field settings")

Why This Fits : Field configurations allow you to set the Attribute field as hidden, optional, or required for different issue types, directly meeting the requirements.

Why Other Options Are Incorrect :

Screens (Option B) :

Screens define which fields appear during issue operations (e.g., Create, Edit, View). While hiding a field on a screen for Epics could make it appear hidden, screens are not issue type-specific unless combined with a screen scheme . Screens also cannot enforce required or optional behavior, which is handled by field configurations.

Extract from Documentation :

Screens control which fields are displayed but do not manage required or optional behavior. Use field configurations for field behavior.

(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")

Custom field contexts (Option C) :

Custom field contexts define the options and default values for a custom field across projects or issue types. They do not control whether a field is hidden, optional, or required, which is managed by field configurations.

Extract from Documentation :

Custom field contexts set options and defaults for fields, not their visibility or required status. Use field configurations for behavior.

(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")

Screen schemes (Option D) :

Screen schemes map screens to issue operations (e.g., Create, Edit) for issue types. They control which fields appear on screens but do not manage whether fields are required or optional, which is handled by field configurations.

Extract from Documentation :

Screen schemes assign screens to issue types but do not control field behavior like required or hidden. Use field configurations for this.

(Source: Atlassian Support Documentation, "Configure screen schemes in Jira Cloud")

Additional Notes :

Steps to configure :

Create three field configurations in Settings > Issues > Field configurations :

Epic: Set Attribute to Hidden .

Story: Set Attribute to Optional .

Bug: Set Attribute to Required .

Create a field configuration scheme in Settings > Issues > Field configuration schemes and map each configuration to the respective issue type (Epic, Story, Bug).

Assign the scheme to the project in Project settings > Fields .

Configuring field configurations requires Jira administrator privileges.

Ensure the Attribute custom field is included on the relevant screens (except for Epics, where it is hidden) to avoid conflicts.

The question involves managing versions in a company-managed project in Jira Software Cloud. Maia wants to move all issues from version 1.1 to version 1.2 and remove version 1.1 as an available option in the Fix Versions field. The two operations that meet both requirements are Archive and Merge .

Explanation of the Correct Answers :

Archive (Option B) :

Archiving a version removes it from the Fix Versions field as an available option for new issues, while preserving the version’s association with existing issues. Additionally, archiving allows you to move issues to another version (e.g., version 1.2) during the process, meeting both requirements.

Exact Extract from Documentation :

Archive a version

Archiving a version removes it from the list of available versions in fields like Fix Versions, so it can’t be selected for new issues. You can also move issues to another version during the archiving process.

To archive a version:

Go to your project’s Releases page.

Find the version (e.g., version 1.1) and select Archive .

Optionally, choose to move issues to another version (e.g., version 1.2). Archived versions are still visible in reports and issue details but are no longer selectable in fields. Note : You need project admin permissions to archive versions. (Source: Atlassian Support Documentation, "Manage versions in company-managed projects")

Why This Fits : Archiving version 1.1 removes it from the Fix Versions field, preventing it from being selected for new issues, and allows Maia to move all issues to version 1.2 during the archiving process, fulfilling both requirements.

Merge (Option D) :

Merging a version moves all issues from one version (e.g., version 1.1) to another (e.g., version 1.2) and deletes the source version, effectively removing it from the Fix Versions field. This meets both requirements, as it reassigns issues and eliminates version 1.1 as an available option.

Exact Extract from Documentation :

Merge versions

Merging versions allows you to combine two versions by moving all issues from one version to another. The source version is deleted after the merge.

To merge versions:

Go to your project’s Releases page.

Find the version to merge (e.g., version 1.1) and select Merge .

Choose the target version (e.g., version 1.2) to move issues to. After merging, the source version (version 1.1) is removed from the Fix Versions field and is no longer available for selection. Note : Merging is permanent and cannot be undone, so ensure the target version is correct. (Source: Atlassian Support Documentation, "Manage versions in company-managed projects")

Why This Fits : Merging version 1.1 into version 1.2 moves all issues to version 1.2 and deletes version 1.1, ensuring it is no longer an option in the Fix Versions field, thus meeting both requirements.

Why Other Options Are Incorrect :

Delete (Option A) :

Deleting a version removes it from the Fix Versions field, but it also removes the version from all issues associated with it without reassigning them to another version. This does not meet the requirement to move issues to version 1.2.

Extract from Documentation :

Delete a version

Deleting a version removes it from the project and clears it from the Fix Versions field of all associated issues. Issues are not reassigned to another version automatically.

Note : Use caution, as this action cannot be undone, and issues lose their version association.

(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")

Build and release (Option C) :

Building and releasing a version marks it as complete and moves unresolved issues to another version, but it does not remove the version from the Fix Versions field. Released versions remain selectable unless archived or deleted.

Extract from Documentation :

Release a version

Releasing a version marks it as complete and optionally moves unresolved issues to another version. The released version remains available in the Fix Versions field unless archived.

(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")

Additional Notes :

Both Archive and Merge are suitable, but they have different implications:

Archiving preserves version 1.1 in reports and issue histories, making it ideal if historical data needs to be retained.

Merging permanently deletes version 1.1, which may be preferred if the version is no longer relevant.

The operations require project admin permissions in a company-managed project, and the Releases page is accessed via Project Settings > Releases .

The requirements for the new Jira project include a central backlog, burndown chart, different QA processes for defect types, and the ability to share schemes with another project. The company-managed Scrum project type (Option B) best fulfills all these requirements due to its support for Scrum boards, burndown charts, flexible workflows, and shared configurations.

Explanation of the Correct Answer (Option B) :

Manage and prioritize all work from a central backlog :

Company-managed Scrum projects include a Scrum board with a central backlog where issues (e.g., Stories, Defects) can be managed and prioritized.

Exact Extract from Documentation :

Company-managed Scrum projects

Company-managed Scrum projects provide a Scrum board with a central backlog for managing and prioritizing work.

To access:

Go to Project > Backlog .

Prioritize issues by dragging and dropping. Note : The backlog supports all issue types in the project. (Source: Atlassian Support Documentation, "Manage Scrum projects in Jira Cloud")

Track progress with a burndown chart :

Company-managed Scrum projects support burndown charts in sprint reports, which track progress based on Story Points or issue count during a sprint.

Exact Extract from Documentation :

Burndown charts in Scrum projects

Company-managed Scrum projects include burndown charts in sprint reports to track progress.

To view:

Go to Project > Reports > Burndown Chart .

Select the sprint to view progress. Note : Burndown charts require sprints and Story Points or issue counts. (Source: Atlassian Support Documentation, "Manage Scrum projects in Jira Cloud")

Move pre-production defects and production defects through a different QA process :

Company-managed projects allow different issue types (e.g., Pre-production Defect, Production Defect) to use distinct workflows via a workflow scheme . This enables separate QA processes (e.g., different statuses or transitions) for each defect type.

Exact Extract from Documentation :

Configure workflows in company-managed projects

A workflow scheme maps workflows to issue types. Different issue types (e.g., Pre-production Defect, Production Defect) can use different workflows to support unique processes.

To configure:

Go to Settings > Issues > Workflow schemes .

Assign workflows to issue types in the project’s scheme. Note : Company-managed projects support complex workflow configurations. (Source: Atlassian Support Documentation, "Configure workflow schemes")

Have the project share its schemes with another project in the future :

Company-managed projects use shared configurations (e.g., permission schemes, workflow schemes, issue type schemes) that can be reused by other projects. This allows the new project to share its schemes with another project in the future.

Exact Extract from Documentation :

Shared configurations in company-managed projects

Company-managed projects use schemes (e.g., workflow, permission, issue type) that can be shared across multiple projects.

To share:

Create a project with a shared configuration in Settings > Projects > Create project .

Select the same schemes for another project. Note : Team-managed projects have project-specific configurations and cannot share schemes. (Source: Atlassian Support Documentation, "Create a project in Jira Cloud")

Why This Fits : The company-managed Scrum project type supports a central backlog, burndown charts, distinct workflows for defect types, and shared schemes, fully meeting all requirements.

Why Other Options Are Incorrect :

Company-managed Kanban (Option A) :

While company-managed Kanban projects support a central backlog (Kanban board) and shared schemes, they do not natively provide burndown charts , which are specific to Scrum projects for tracking sprint progress. Additionally, while different workflows for defect types are possible, Kanban projects are less aligned with sprint-based tracking like burndown charts.

Extract from Documentation :

Company-managed Kanban projects use a Kanban board but do not include burndown charts, which are specific to Scrum sprints.

(Source: Atlassian Support Documentation, "Manage Kanban projects in Jira Cloud")

Team-managed Scrum (Option C) :

Team-managed Scrum projects support a backlog, burndown charts, and simplified workflows. However, they do not support shared schemes, as configurations (e.g., workflows, permissions) are project-specific and cannot be reused by other projects. Additionally, team-managed projects have limited workflow flexibility, making it harder to define distinct QA processes for defect types.

Extract from Documentation :

Team-managed projects have project-specific configurations and cannot share schemes with other projects. Workflows are simplified and may not support complex processes for multiple issue types.

(Source: Atlassian Support Documentation, "Manage team-managed projects in Jira Cloud")

Team-managed Kanban (Option D) :

Team-managed Kanban projects support a Kanban board but lack burndown charts , as they do not use sprints. They also have project-specific configurations, preventing scheme sharing, and limited workflow flexibility for distinct QA processes.

Extract from Documentation :

Team-managed Kanban projects do not support burndown charts or shared schemes. Workflows are project-specific and simplified.

(Source: Atlassian Support Documentation, "Manage team-managed projects in Jira Cloud")

Additional Notes :

Creating a company-managed Scrum project requires Jira administrator privileges ( Settings > Projects > Create project ).

The project can be configured with a Scrum board , workflow scheme for distinct defect workflows, and shared schemes for future projects.

Burndown charts require sprints and Story Points or issue counts to be configured.

Adding a new issue type to a company-managed project requires updating configurations that map issue types to various settings (e.g., screens, workflows, fields). The configuration item that is definitely not impacted is the issue security scheme (Option C), as it controls issue visibility and is not directly tied to issue types.

Explanation of the Correct Answer (Option C) :

An issue security scheme defines security levels that restrict which users can view issues in a project, based on criteria like users, groups, or roles. It is applied at the project level and is not specific to issue types. Adding a new issue type does not require changes to the issue security scheme, as security levels apply to all issues in the project regardless of their type.

Exact Extract from Documentation :

Configure issue security schemes

Issue security schemes define security levels to control who can view issues in a project.

Impact of issue types :

Security levels are applied to all issues in a project, regardless of issue type.

Adding a new issue type does not affect the issue security scheme. To check:

Go to Project settings > Issue security .

Review the security levels and their criteria. Note : Issue security is independent of issue type configurations. (Source: Atlassian Support Documentation, "Configure issue security schemes")

Why This Fits : The issue security scheme is not impacted by adding a new issue type, as it operates at the project level and does not depend on issue type configurations, making Option C the correct answer.

Why Other Options Are Incorrect :

Issue layout (Option A) :

The issue layout defines which fields are displayed or hidden in the issue view for each issue type. Adding a new issue type may require configuring a new issue layout to specify field visibility for that type, impacting this configuration.

Extract from Documentation :

Issue layouts are configured per issue type in Project settings > Issue layout . Adding a new issue type may require a new layout configuration.

(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")

Issue type screen scheme (Option B) :

The issue type screen scheme maps screens to issue types for operations (Create, Edit, View). Adding a new issue type requires assigning a screen to it in the scheme, impacting this configuration.

Extract from Documentation :

Adding a new issue type requires updating the issue type screen scheme to assign screens for the new type.

(Source: Atlassian Support Documentation, "Configure screen schemes in Jira Cloud")

Workflow scheme (Option D) :

The workflow scheme maps workflows to issue types. Adding a new issue type requires assigning a workflow to it in the scheme, impacting this configuration.

Extract from Documentation :

Adding a new issue type requires updating the workflow scheme to assign a workflow for the new type.

(Source: Atlassian Support Documentation, "Configure workflow schemes")

Field configuration scheme (Option E) :

The field configuration scheme maps field configurations to issue types, defining field behavior (required, optional, hidden). Adding a new issue type may require assigning a field configuration to it, impacting this configuration.

Extract from Documentation :

Adding a new issue type may require updating the field configuration scheme to assign a configuration for the new type.

(Source: Atlassian Support Documentation, "Configure field settings")

Additional Notes :

Steps to add a new issue type :

Add the issue type to the project’s issue type scheme in Project settings > Issue types .

Update the issue type screen scheme , workflow scheme , and field configuration scheme to include the new issue type.

Configure the issue layout for the new issue type if needed.

These changes require Jira administrator privileges for schemes and project admin privileges for issue layout.

The issue security scheme remains unaffected, as it applies to all issues in the project.

Okay, let's analyze this question again with the revised options.

The requirement is to prevent anyone from editing an issue when it resides in a specific workflow status .

As established previously:

Conditions (A): Control whether a transition out of or into a status can occur. They check criteria before a transition starts. They don't prevent editing while an issue is sitting in a status.

Post Functions (Implied by B & C): Actions that execute after a transition is successfully completed (e.g., updating a field, sending a notification). They don't affect editability within the status itself.

Triggers (D): Automatically initiate a workflow transition based on external events (like code commits). Not relevant to editing permissions within a status.

The correct way to achieve this in Jira is by setting a Status Property :

Navigate to Workflow configuration.

Select the relevant status.

Go to its 'Properties'.

Add a property: jira.issue.editable with the value false.