Overview
| Excerpt |
|---|
This article explains the best practice for migrating Jira projects by following CMJ Compatibility Matrix. |
Best Practice
The Configuration Manager for Jira app (CMJ) can migrate Project with issues along with the associated attachments. The Configuration Manager app is designed to support the export and import snapshots from different Jira versions. You can migrate projects from one Jira version to another.
...
Example: Configuration Manager for Jira v6.6.8 is supported for Jira versions between 7.8.0 to 8.11.0. In the 6.6.8 version of CMJ, any version of Jira can be installed between v7.8.0 to v8.11.0 in the source and target, but the CMJ app version should be identical to v6.6.8 at both places.
Important An important point to remember: If the Jira versions are different, the target instance shouldn't be running on an older version than the source instance.
...
For more information, refer to this link: https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/4784162/Compatibility+Matrix
If the Jira versions are close generally they don't differ in any major features and so it is absolutely safe to use CMJ to create and deploy 100% valid and full snapshots. Also, you don't need to use the same version of CMJ but it is recommended to use close versions if the same is not possible, so you could get the same set of features and object support.
Snapshot compatibility between Jira versions
Snapshots created on versions of Jira before Jira 6.3 will remove all members of the "Transition Issue" permission in permission schemes when deployed on Jira 6.3 and above.
Some Jira versions introduce new configuration objects and remove others so a snapshot taken on one version might not always work on another.