Page Comparison

This document details on how JMWE JMCF is now supporting the migration of one Jira instance to another using Botron’s Configuration Manager.

Background:

Before 62.2.0 when a Jira instance with JMWE workflow extensions JMCF custom fields is migrated to another Jira instance only some part of the configuration is retained as it is. For example: Workflow extensions that operated on the custom fields, issue link types, resolution, groups, project roles, and many more failed to be recognized in the new instance. Now with JMWE 6

• Groovy scripts using custom fields by their id ( issue.get(“customfield_10100”)) were not replaced in the destination instance

• Statuses 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 post-function custom fields is replaced with the new object created in the destination Jira instance.

Limitation:

However there are certains limitation to what can be retained.

...

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.