Skip to end of banner
Go to start of banner

Best Practice: Compatibility of Configuration Manager for Jira app versions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Overview

This article explains the compatibility Configuration Manager for Jira app versions.

Best Practice

Generally, the Configuration Manager for Jira (CMJ) app can be used across different versions of Jira.

The version of Configuration Manager for Jira (CMJ) could differ on the source and target Jira instance as well as the Jira versions could differ. However, you still need to have in mind that newer Jira versions are introducing new features compared to previous versions. The same is valid for Configuration Manager for Jira(CMJ), the latest versions of CMJ compatible with the latest versions of Jira. When using an older version of CMJ on a newer Jira version it is possible that some objects are not exported if they are not supported by that CMJ version. If you deploy that snapshot then on a new instance you may expect those objects to appear but they will not because they are not supported by 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

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.


  • No labels