Versions Compared

Old Version 1

changes.mady.by.user Daniel Barrow

Saved on

compared with

New Version Current

changes.mady.by.user Daniel Barrow

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The JMWE app has an automated migration path and can be migrated from Jira Server/Data Center; migration requires JMWE for Jira Server/Data Center version 7.2.0 or later. Migration is currently supported using Jira Cloud Migration Assistant (JCMA) automation only.

Note

Be aware that JMWE migration using JCMA is currently in Beta, so you may wish to test the JMWE migration in a trial or test Cloud instance.

Note: If you have already migrated to the Cloud and need information regarding how to fix errors, see the Post Migration page.

Info

You are viewing the documentation for Jira Data Center/Server.

On This Page

Table of Contents
minLevel1
maxLevel2
outlinefalse
typelist
printablefalse

Before you start

  1. Make sure you are running JMWE for Server/Data Center version 7.2.0 or later.

  2. Review the Feature comparison between JMWE for Jira Data Center/Server and JMWE for Jira Cloud.

  3. 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 migrated, but due to some feature differences, it is highly recommended that you verify these actions after migration.

  • 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.