You are using a bulk move operation to migrate issues in a company-managed project from...

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 arestatuses(Option A) andrequired 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’sworkflow 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 chooseBulk 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, makingstatusesa potential element that needs to change.

Required fields (Option C):

Different issue types can be associated with differentfield 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 issuetype (e.g., a custom field or system field likeDue 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 inSettings > 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, makingrequired fieldsa potential element that needs to change.

Why Other Options Are Incorrect:

Priorities (Option B):

Thepriorityfield 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 byrequired 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):

Theresolutionfield 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):

Thelabelsfield 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 likeLabelsare 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 viaIssues > Search for issues > Bulkchange > Move issues, requiring theMove Issuespermission.

The need to changestatusesandrequired fieldsdepends 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 thatmightneed to change.