Botron Configuration Manager for Jira is a third-party app that can be used, among other things, to transfer Jira configuration and data between different Jira servers . This article lists support to the migration of the (instances).
JMWE 6.2.0 and above integrates with Configuration Manager to support migrating workflows containing JMWE conditions, validators and post-functions with minimal effort using Botron Configuration Manager.
On this page:
Table of Contents |
---|
Pre-requisites
Before migrating data from one instance to another make sure you have the same version of JMWE and Configuration Manager on both the instances.
Limitations
Except for the following cases, most of JMWE configuration is migrated by Botron without any disruption:
Groovy templates that have a reference to the custom field by their Id’s are not modified
Shared Groovy scripts are not migrated to the destination instance. Note, this might be implemented in the future.
Groovy Scripts and Templates that have include a reference to the IssueConstants (like Resolution, Priority, etc) by their ID will not be replacedupdated. For example, a Set field value post-function that returns the Id,
10008
to set the priority of the issue will not be replaced to Id of the Priority object created in the new destination instance.
Related articles
Filter by label (Content by label) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|