After migration issues with JMWE: some extensions always load empty, then breaks

[Team Atlassian]

Hi all!

Context:

We are migrating projects (and all necessary data) from a Jira Data Center to Jira Cloud. The customer uses JMWE (Jira Misc Workflow Extensions) for multiple automational task on the workflows (thousands of them).

Issue: 

According to our migration testings, there are multiple times when certain extensions after migration continously load empty. This situation makes the extensions unusable, uneditable and essentally broken.
According to Appfire, the loading of the extensions are handled by Jira, while the migration is handled by JCMA. In case of the problem only a retried migration or a delete and recreate method can be used.

As you can already guessed, none of the above method is acceptable, as the customer is in a strictly regulated sector, and has to maintain low downtime. All migration has to happen from 0 to 100 considering the project in a strict time frame, and remigrations are not acceptable.

Quetion the communnity (you guys :) ): 

Is there a supported method or best practice to fully and correctly migration these extension without the need to manually recheck and correct them after migration?

Thank you for your time!

[Gaurav Chavda]

Hi,

Probably this is not the answers, but I would like to understand this situation in more detail to see if I can answer or not. 

is this issue specific to data or configuration? i.e, migrated issues becomes unusable? or automation triggers are no longer performing as expected. 

I feel like, even if JCMA migrates this plugin configurations but certain broken references can occur if:

App versions differ between DC and Cloud

Field IDs, option IDs, or project keys change mid-migration

Once broken, these items appear as "loading forever" because the configuration references are missing or corrupted.

Could you provide some samples/examples to look/review? 

Thanks
Gaurav

[Oleksii Melnyk]

Hi @Team Atlassian Did you ask Appfires support in this case?
https://appfire.atlassian.net/servicedesk/customer/portal/11/user/login?destination=portal%2F11

In a similar situation, we allowed tickets to be created, but the client's team did not process them further until we fixed the workflow.