Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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

Background:

Before 6.2.0 when a Jira instance with JMWE workflow extensions 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.2.0, the object reference in the post-function is replaced with the new object created in the destination Jira instance.

Limitation:

However there are certains limitation to what can be retained.

  1. If you are trying to set an object with its Id, then the Id is not replaced to the Id of the new object in the destination instance. For example, if you are setting the Priority field with an id 10010, and the id of the new object created for the same is 10213, the id will not be replaced in the post-function.

  • No labels