Problem description: Loss of JMWE configuration during project migration in Jira Cloud

Eric Roetenberg

Context:
Within our Jira Cloud environment, we manage the project ESMR, which uses five separate workflows. These workflows are relatively complex and make intensive use of JMWE (Jira Misc Workflow Extensions).
Each workflow contains multiple transitions, with an average of between 5 and 10 validators, conditions and postfunctions configured per transition. A significant portion of these are built using JMWE functionalities.

Problem:
We recently performed an export of the ESMR project with the goal of importing it into another Jira Cloud environment, which also has JMWE installed as an app.
However, after completing the project import, we find that all JMWE-specific elements (validators and postfunctions) are missing from the imported workflows. Only the standard Jira components have been retained. This results in an incomplete and non-functioning workflow process.
Given the size and complexity of the workflows, manually rebuilding all JMWE configuration is a very time-consuming and error-prone task.

Ask the communnity :
Is there a supported method or best practice to fully and correctly export and import a Jira project with JMWE configuration between two Jira Cloud environments?
- If anything, are there tools or scripts available that can backup or migrate JMWE-specific workflow components?
- If this behavior is a limitation or bug in the way Jira or JMWE handles project exports, is there visibility into a solution or workaround?
Objective:
We are looking for a way to reliably and efficiently migrate the entire workflow configuration - including all JMWE extensions - to another Jira Cloud environment, without having to manually rebuild everything.

Grtz. Eric Roetenberg

 

Walter Buggenhout

Hi @Eric Roetenberg,

I am not entirely sure what you mean by a 'project export'. There is a copy data feature available that does allow you to copy projects between different cloud sites. However, this (native) feature does have a lot of limitations still, as you can read in this support article. App data is not included in that copy data capability today.

Since the native feature does not support migrating app features, I would be surprised if there was an export / import alternative that would, since alternatives usually are limited by the API endpoints Atlassian provides for 3rd parties to use.

The best and most certain way to check would be to reach out to the app vendor directly though the support channel listed on the app's marketplace listing.

Hope this helps!