Overview
Configuration Manager for Jira (CMJ) by Botron is a powerful tool that automates the transfer of Jira configurations and data between different Jira servers and DataCenter instances.
Since its first release, Configuration Manager for Jira has provided built-in integrations for the most widely used apps, including JSU Automation Suite for Jira Workflows for Server and Data Center. Users of JSU can migrate most of their workflow configurations with minimal effort.
As of release 2.27.0, JSU provides full integration for CMJ. Thanks to this integration, the migration of all JSU configurations including global settings, project variables, custom fields, conditions, validators, and post-functions is officially supported.
JSU supports native integration for Botron Configuration Manager for Jira version 6.6.6 and higher
It is recommended to verify and test the app configuration data migration in a staging environment before deploying it in production.
Pre-requisites
Ensure both the source and target instance have the same version of JSU for Jira Server and Data Center (2.27.0 and higher)
It's important for you to install the same version of JSU on both instances!
Ensure Botron Configuration Manager for Jira (6.6.6 and higher) is installed on both the source and target instance
Ensure the integration is active on both the source and target instance
Limitations
Built-in integration of Configuration Manager for Jira supports JSU Servers and Data Center version 1.4.9 to 2.7.0. If users are using other versions of JSU, it is recommended to upgrade to version 2.27.0 to have full integration support.
Built-in integration of Configuration Manager for Jira does not support migration of JSU Global Setting and Project Variables.
The native integration for Configuration Manager for Jira requires Jira from version 7.2, and CMJ from version 6.6.6 or later.
Integration Notes
Disabled Modules
If Configuration Manager for Jira is not installed in the system, users may notice some of the JSU modules are disabled by default. This is expected behavior. These modules will be automatically activated once CMJ is installed.
