The JMWE app has an automated migration path and can be migrated from Jira Server/Data Center (version 7.2.0 and later) using Jira Cloud Migration Assistant (JCMA) automation. Be aware that JMWE’s Cloud migration using JCMA is currently in beta, so you may wish to test the JMWE migration in a trial/test Cloud instance.
...
| Table of Contents |
|---|
| minLevel | 1 |
|---|
| maxLevel | 3 |
|---|
| outline | true |
|---|
| style | none |
|---|
| exclude | Please note |
|---|
|
Before you start
Make sure you are running JMWE for Server/Data Center version 7.2.0 or later.
Read and follow the instructions in Atlassian’s documentation on Jira Cloud Migration Assistant (JCMA).
| Note |
|---|
Please note:Currently, Shared actions, Event-based actions, and Scheduled actions are not migrated. You must recreate these manually on your Cloud instance. Any JMWE conditions, validators, and/or post-functions where you employed Groovy scripting will throw errors and will need to be updated with either Jira expressions or Nunjucks expressions/scripts. Because Jira Cloud runs post-functions after a transition completes, there are no error handling capabilities in Jira Cloud to prevent transitions from completing. Post-functions that include error handling in your Server/DC instance will display warnings on the Post migration page. The Return to Previous Status post-function is not migrated from Server as there is no equivalent on the Cloud version. JCMA will report this in the logs on the server side during migration.
|
...