Set up Jira Cloud
Learn how to set up Jira Cloud and integrate it with other products and applications.
Move multiple issues
You need to have the relevant project permissions to move issues.
You can bulk move issues to other projects on your Jira site. This can help you keep your project workspaces clean and all their issues relevant to the team who’s working on them.
Move multiple issues from the backlog
You can only move multiple issues from the backlog if you’re in a software project.
To move multiple issues from the backlog:
Select multiple issues from the backlog. You can either:
use the issue checkboxes
hold Ctrl (Windows) or Command (Mac) while selecting issues
hold the Shift key to select a group of adjacent issues
Select More actions (•••) on one of the selected issues, then select Bulk change.
Select Move Issues and select Next.
Select a destination project and issue type, and select Next.
Select a value for any required fields for this move, and if available, decide whether you'd like to send email notifications. Select Next.
Review your changes and select Confirm, then Acknowledge.
Move multiple issues from the board
You can only move multiple issues from the board if you’re in a software project.
To move multiple issues from the board:
Select multiple issues from the board. You can either:
hold Ctrl (Windows) or Command (Mac) while selecting issues
hold the Shift key to select a group of adjacent issues
Right-click or select More actions (•••) on one of the selected issues, then select Bulk change.
Select Move Issues and select Next.
Select a destination project and issue type, and select Next.
Select a value for any required fields for this move, and if available, decide whether you'd like to send email notifications. Select Next.
Review your changes and select Confirm, then Acknowledge.
Move multiple issues from the issue navigator
To move multiple issues from the issue navigator:
Adjust the search criteria to show the appropriate list of issues.
Select Import and bulk change issues (•••) and choose Bulk Change all <n> issues.
Select the issues you'd like to perform the bulk operation on, and select Next.
Select Move Issues and select Next.
Select a destination project and issue type, and select Next.
Select a value for any required fields for this move, and if available, decide whether you'd like to send email notifications. Select Next.
Review your changes and select Confirm, then Acknowledge.
Things to keep in mind when moving multiple issues
Select destination projects and issue types
The issues in your destination project might have different settings than your source project, even if they are named the same. If issue types use different workflows, you may lose data when bulk moving issues. So, you need to map the status and fields while selecting the destination project and issue types. Your target project and issue type will determine the additional steps that will be needed to migrate status and fields. If your issues have subtasks, then you will need to move the subtasks to the destination project as well.
Map statuses
The issue type workflow in your destination project might use different statuses than the issue type workflow in the source project. It is best to check with your source and destination project leads to know more about the projects' workflow. Multiple workflows can be active simultaneously, and some statuses that are associated with a collection of issues may not be valid in the target workflow.
After selecting the destination project and issue types for bulk move, you can map the statuses from your source project to the right statuses in your new workflow by selecting the status your issues should be in after the move.
When mapping statuses, it's a good idea to map issues to similar status categories, or you might throw off a project team looking to pick up their next task.
Work with your project leads to understand what statuses mappings make the most sense before completing your bulk move operation.
Update fields
The destination project’s issue types may have different field settings than the source project. You can either update the field’s value or retain the field’s current value.
After mapping the statuses, you can update the values for any required fields. For each field listed, update the value that should appear on the issues you’re moving, or select Retain to leave the field’s value unchanged.
While selecting Retain, the fields need to be of the same custom field type and they need to be named the same. Jira might not display the value of the field, but the value is still stored in the background.
More about editing fields for multiple issues
Was this helpful?
Still need help?
The Atlassian Community is here for you.