Overview
| Excerpt |
|---|
This article explains the compatibility best practice of Migrating data between Jira Servers using Configuration Manager for Jira app versions. |
Best Practice
Generally, the Configuration Manager for Jira (CMJ) app can be used across different versions of Jira.
...
If the Jira versions are close, generally they don't differ in any major features 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.
The version of Configuration Manager for JIRA(CMJ) on the source and target instances should be identical and in case, if the versions are different, then the target instance shouldn't be running an older version than the source instance.
We would suggest you run the same version of CMJ i.e v6.6.8 in both the PROD and TEST instances.
Please check the compatibility matrix to make sure the version of the Configuration Manager for JIRA(CMJ) is identical between the Data Center Jira Instance and Server Instance.
For more information, please refer to the below link:
https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/4784162/Compatibility+Matrix
you can migrate projects from one Jira version to another as the Configuration Manager for Jira is designed to support exporting and importing snapshots from different Jira versions.
The Configuration Manager for Jira app (CMJ) can migrate Project with issues along with the associated attachments.
Yes, it's always ideal to have the same version of Jira running on both the Source and Target instances. However, with our latest versions of Configuration Manager for Jira app, one can have two different Jira versions on Source and Target instances but provided the version of Configuration Manager for Jira is identical.
Example - Configuration Manager for Jira v6.6.8 is supported for Jira version between 7.8.0 to 8.11.0, If using this version, then two different Jira versions between 7.8.0 to 8.11.0 can be installed in Source and Target, but the CMJ app version should be identical v6.6.8 in both source and target.
Another important point to remember is, if the Jira versions are different, then the target instance shouldn't be running an older version than the source instance.
Example -
If running Jira Source v7.8.0 and Target v8.10.0, then CMJ Works perfectly.
However, if Jira Source is v8.10.0 and target v7.9.0, then the CMJ might not give accurate results.