Overview
| Excerpt |
|---|
This article explains the best practice of Migrating data between Jira Servers using practices for migrating Jira projects from one Jira data center to another by following the Configuration Manager for Jira app(CMJ) Compatibility Matrix. |
Best
...
Practices
Generally, the The Configuration Manager for Jira app (CMJ) app can be used across different versions of Jira.The can migrate projects with issues and associated attachments. The Configuration Manager app is designed to support the export and import of snapshots to/from different Jira versions. You can migrate projects from one Jira data center version to another Jira data center.
| Info |
|---|
Having the same version of Jira running on both source and target instances is always ideal. However, with the latest version of Configuration Manager for |
...
Jira app one can have two different Jira versions on the source and target |
...
instances provided the version of Configuration Manager for Jira app is identical. |
Use case: Configuration Manager for Jira v6.13.5 works for Jira versions between 8.0.0 and 9.11.1. In the 6.13.5 version of Configuration Manager for Jira(CMJ),
...
Here is a link to a compatibility matrix - https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/4784162/Compatibility+Matrix
Also, here is an article with the object support for CMJ - https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/4784151/Configuration+Object+Support+Matrix
...
any version of Jira can be installed between v8.0.0 and v9.11.1 in the source and target.
| Info |
|---|
If the Jira versions differ, the target instance should not be running on an older version than the source instance. |
Use case: If the Jira source instance is on v8.0.0 and the target is on v9.11.1, CMJ works perfectly. However, if the Jira source instance is on v9.11.1 and the target is on v8.0.0, the CMJ might not give accurate results.
| Info |
|---|
If the Jira versions are within the same base version, 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 |
...
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.
...
. |
Use case: Jira source instance is on v8.0.0 and the target is on v8.1.0, CMJ is absolutely safe to create and deploy valid and full snapshots.
| Info |
|---|
If the Configuration Manager for Jira(CMJ) versions are different in source and target, you need to make sure that the Configuration Manager version on the target instance needs to be the same or newer than the one in the source. |
Use case: If the CMJ version is 6.12.5 in the source and 6.13.5 in the target, then the deployment will be successful, but if the CMJ version is 6.13.5 in the source and 6.12.5 in the target, the deployment will not be successful.
It is always suggested to check the compatibility matrix to make sure the version versions of the Configuration Manager for JIRAJira (CMJ) is identical are the same between the Data Center Target Jira Instance and Server Instanceinstance and the Source Jira 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 resultsthis link: Compatibility Matrix
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.