Moving an issue

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

When teams or projects change, you can move issues between Jira projects to make sure everyone is on top of the work that needs to get done. 

Before you begin

Make sure you have the Move Issues and Create Issues project permissions. Your Jira administrator can help assign any needed permissions. If you want to move multiple issues between projects at the same time, check out the Editing multiple issues at the same time page.

tip/resting Created with Sketch.

We're rolling out a new issue view, with a consistent appearance across Jira and one screen to view and edit. It looks a little different and some procedures have changed slightly, so take a look at our updates page to see what's changed and get the latest updates and Work in the new issue view for info on how to complete common tasks. To turn the new issue view on or off in Jira Software and Jira Core for now, head to Your profile and settings () > Personal settings and toggle the switch for the New Jira issue view.

The new issue view is permanently on for all business boards and next-gen software projects.

If you don't see the Personal settings option when you click your avatar, the switch to turn the new issue view on or off will appear under Profile.

How to move an issue

  1. View the issue that you wish to move and click more (•••) > Move
  2. Complete the steps required

     What to update Details 
    Issue type If your issue is a custom issue type that does not exist in your target project, you must select a new issue type. 
    Issue status You may have set up custom issue statuses as part of a workflow. If you have assigned a custom status to your issue, and it does not exist in your target project, you must select a new issue status for your issue. You cannot arbitrarily change the issue status, i.e. the option to change the issue status will only appear if you are required to change it.
    Custom fields If you have defined required custom fields for your issue that do not exist in your target project, you must set values for them. You will only be prompted to enter the values for required custom fields in the target project that are missing values. If the custom fields of your original project also exist in your target project, and these custom fields are not required in the target project, you may need to set values for them, to move the issue successfully. If you wish to change the existing values for other fields on your issue, you can do this after the move is complete.
  3. Review your changes and click Move

  • All sub-tasks will be moved with the parent issue.  
  • If you are moving an epic, you will need to move all issues within that epic separately.


If restricted comments appear to be removed after moving the issue, ee this article: Restricted comments disappear after moving an issue to a new project.

Last modified on May 30, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.