When moving issues between two company-managed projects with different field configurations using a bulk operation, certain fields may need to be updated due to differences in workflows, field configurations, or project-specific settings. The field that willdefinitelybe updated isStatus(Option E), as issues must be mapped to a valid status in the target project’s workflow.
Explanation of the Correct Answer (Option E):
Each company-managed project can have its ownworkflow scheme, which assigns workflows to issue types. When moving issues between projects, the source project’s workflow may have different statuses than the target project’s workflow. During a bulk move, you must map the current status of each issue to a valid status in the target project’s workflow, as the source status may not exist in the target workflow. This status mapping is a mandatory step in the bulk move process, ensuring thatStatusis always updated.
Exact Extract from Documentation:
Move issues between projects
When moving issues to a different project in Jira Cloud, you must map the issue’s status to a valid status in the target project’s workflow.
To move issues:
Select issues and chooseBulk change>Move issues.
Choose the target project and issue type.
Map the source status to a target status for each issue type.Note: Status mapping is required because projects may use different workflows with distinct statuses.(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
Why This Fits: The bulk move operation always requires mapping theStatusfield to a valid status in the target project’s workflow, makingStatusthe field that will definitely be updated.
Why Other Options Are Incorrect:
Assignee (Option A):
TheAssigneefield is not necessarily updated during a move. If the assignee is a valid user in the target project and has theAssignable Userpermission, the assignee remains unchanged. Only if the assignee is invalid (e.g., lacks permissions) might you need to update it, but this is not guaranteed.
Extract from Documentation:
TheAssigneefield is preserved during a move unless the user is not assignable in the target project, in which case you may be prompted to choose a new assignee.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
Custom fields may require updates if the target project’s field configuration mandates values not required in the source project. This is not always necessary.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
TheResolution Dateis set by workflow transitions, not directly by moving issues. It remains unchanged unless the move alters the resolution.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
Components (Option D):
Componentsare project-specific, and the target project may have different components. During a move, you may need to map or clear components if the source components do not exist in the target project. However, this is not guaranteed, as components may be compatible or optional.
Extract from Documentation:
Components may need to be mapped or cleared if the target project has different components, but this is not always required.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
Additional Notes:
The bulk move operation is performed viaIssues > Search for issues > Bulk change > Move issues, requiring theMove Issuespermission.
The mandatory status mapping ensures compliance with the target project’s workflow, makingStatusthe only field always updated.
Other fields (e.g.,Assignee,Custom fields) may be updated depending on configurations, but onlyStatusis certain.
[:, Atlassian Support Documentation:Move issues in Jira Cloud, Atlassian Support Documentation:Configure advanced work item workflows, ]
