How to move issue to a new project and retain the version fields Affects Version/s and Fix Version/s
Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Purpose
When moving an issue to a new project, the Affects Version/s and Fix Version/s fields may be cleared. This article explains how these values can be retained.
Solution
Jira will only clear the version fields if there's no version number in the destination project that matches exactly the version number in the source project. Jira will not create the version if it doesn't find it in the destination project.
If Jira can match the exact version number (text) in the new project, it will retain the values of the version fields.
Before you move the issues, you need to make sure you either:
- Create a version in the destination project that matches the version in the source project.
- Rename the version in the destination project to match the one in the source project, move the issues, then rename the version back.
- Rename the version in the source project to match the one in the destination project, move the issues, then rename the version back.