This document details how JMCF is now supporting the migration of one Jira instance to another using Botron’s Configuration Manager.
Background:
...
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 (instances).
JMCF 2.2.0
...
and above integrates with Configuration Manager to support migrating JMCF custom fields
...
Groovy scripts using custom fields by their id (
issue.get(“customfield_10100”)) were not replaced in the destination instanceStatuses were not mapped in the destination instance for the Transition Count, Transition Date/Time, Transition Caller and Time in Status custom fields
Fields were not mapped in the destination instance for Last Field Value Change Author and Last Field Value Change Date/Time custom fields
Now with JMWE 2.2.0, the object reference in the custom fields is replaced with the new object created in the destination Jira instance.
Limitation:
...
configuration with minimal effort.
On this page:
| Table of Contents |
|---|
Pre-requisites
Before migrating data from one instance to another make sure you have the same version of JMCF and Configuration Manager on both instances.
Limitations
Except for the following case, all of JMCF configuration is migrated by Botron without any disruption:
Legacy (BeanShell) scripts, which are stored in the field's Description, that refer to custom fields by id (e.g.
issue.get(“customfield_10100”))
...
will not be
...
adjusted with the new
...
field IDs when importing into the destination Jira instance.
Related articles
| Filter by label (Content by label) | ||
|---|---|---|
|