Once an issue has been created, the issue is associated with a project. You can, however, move the issue around from one project to another. This may sound like a very simple process, but there are many steps involved and many things that need to be considered.

First, you need to decide on a new issue type for the issue if the current issue type does not exist in the new project. Second, you will need to map a status for the issue if the target project uses a different workflow. Third, you will need to decide on the values for any mandatory fields that exist in the new project but that do not exist in the current project. Sound like a lot? Luckily, Jira comes with a wizard that is designed to help you address all of these things.

Go through the following steps to start moving an issue:

1. Browse to the issue you wish to move.
2. Click on the Move option in the More menu. This will bring up the Move Issue wizard.

There are essentially four steps in the Move Issue wizard.

The first step is to select which project you wish to move the issue to. You will also need to select the new issue type, as shown in the following screenshot. If the same issue type exists in the new project, you can usually continue and use the same issue type:

The second step allows you to map the current issue to the new project's workflow, as shown in the following screenshot. If the issue's status exists in the target project, the wizard will skip this step:

The third step shows all the fields that exist in the new project but not the current project, as well as those that require a value, as shown in the following screenshot. Again, if there are no fields that require values to be set, this step will be skipped:

The fourth and last step shows you the summary of the changes that will be applied by moving the issue from the source project to the target project. This is your last chance to make sure that all the information is correct. If there are any mistakes, you can go back to step one and start over again. If you are happy with the changes, confirm the move by clicking on Move, as shown in the following screenshot:

Once the issue has been moved, it will be given a new issue key based on the new project. If you access the issue with its old issue key, Jira will automatically redirect you.