When the Jira Cloud Migration Assistant migrates workflow configurations from server to cloud, remote workflow extensions (that is any post functions, conditions, or validators created by an app) is removed from the configuration during the migration. This is to prevent the workflow from not working in Cloud (post migration) if the app is not installed.
Customers with apps that add remote workflow extensions will need to install apps that are 'needed in cloud' and manually recreate their workflow configurations to add post functions, conditions, and validators created by apps.
Example of affected apps (list may not be comprehensive):
|App Name||Marketplace Partner Name||Current migration path instructions (manual)|
|Create on Transition for Jira||Bob Swift Atlassian Apps (an Appfire company)||Read more|
|Jira Misc Workflow Extensions (JMWE)||Innovalog Atlassian Apps (an Appfire company)||Read more|
|JSU Automation Suite for Jira Workflows||Beecom Atlassian Apps (an Appfire company)||Read more|
|ScriptRunner for Jira||Adaptavist||Read more|
|Update on Transition for Jira||Bob Swift Atlassian Apps (an Appfire company)||Read more|
|Xporter - Export issues from Jira||Xpand IT||Read more|
We are adding capabilities to the Cloud Migrations Assistants to migrate app data automatically. This functionality requires Marketplace Partners to build automated migration paths compatible with the Cloud Migration Assistants; they can do so using the App migration platform. The App migration platform does not support apps migrating their own remote workflow extensions.