Overview
| Excerpt |
|---|
This article explains the best practices for migrating Jira projects from one Jira data center to another Jira data center by following the Configuration Manager for Jira(CMJ) Compatibility Matrix. |
...
The Configuration Manager for Jira app (CMJ) can migrate projects with issues along with 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 |
|---|
It is always ideal to have 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), 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 are differentdiffer, the target instance should not be running on an older version than the source instance. |
...
| 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 versions of the Configuration Manager for Jira (CMJ) are the same between the Target Jira instance and the Source Jira instance.
...