This document details how JMCF is now supporting the migration of one Jira instance to another using Botron’s Configuration Manager.
Background:
Before 2.2.0 when a Jira instance with JMCF custom fields is migrated to another Jira instance only some part of the configuration is retained as it is. For example:
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:
BeanShell scripts using custom fields by their id ( issue.get(“customfield_10100”)
) if not edited and saved in the source instance, will not be replaced with the new object in the destination Jira instance.