Copying Cloud to Cloud

Unfortunately, no automated option currently exists for migrating JMWE configurations from one Jira Cloud instance to another. The only option for moving JMWE extensions to another Cloud instance is to manually copy them; this page details recommendations on the order of migration.

Planning the migration

It is highly recommended that you recreate specific categories of extensions in full before moving to the next set; for example, recreating all Shared Actions before configuring individual workflows or other Actions that utilize those Shared Actions will prevent missing Shared Actions in your destination. Overall, the recommended order of operations is:

1. Recreate any Live Fields configurations

2. Recreate Shared Actions and Shared Nunjucks templates

3. Recreate Scheduled Actions and Event-based Actions

4. Lastly, migrate any workflows and rebuild any extensions that have been added directly to them.

Please see the sections below for specific steps and considerations for copying each of the above to your new instance.

Install and setup JMWE at the destination

Before beginning any work, please verify that JMWE Cloud has been installed on your new instance. Additionally, you should copy any specific app settings by checking the JMWE Configuration page on your source and setting those options on your destination.

Recreate Live Fields

Live Fields should be recreated before any other Action or extension - if a Live Field is used in a post function it needs to exist before that post function is created, no matter where the post function exists!

To recreate Live Fields, open the Live Fields administration page in your source instance by going to Apps > Live Fields. For each of your Live Fields configurations, open it by selecting Edit from the Action Menu ( ). In your destination instance, open Live Fields and click Create live fields in the upper right corner of the window; this will start a new configuration. Copy each of the configurations from your source instance to your destination.

Shared actions and Shared Nunjucks templates

Shared Actions and Shared Nunjucks templates are single configurations that can be used in multiple places. Their power - configure and update in one place but use in many places! - is the reason they should be copied to your destination first. Recreating these before adding any other extensions means that they will automatically be available when copying other Actions or configuring your workflows.

To copy these, log into both your source and destination Jira Cloud instances, and go to their respective JMWE Administration pages; click Settings > Apps in the upper right corner and then select the appropriate administration page (e.g. Shared actions). Work down the list, copying the full configuration for each to your destination instance.

For Shared Actions:

1. Make sure the name of the action is identical to the source action.

2. Copy every post function included in the Shared action in the same order they appear in the source instance.

3. Verify that the configuration of each post function in the destination is identical to the source.

For Shared Nunjucks templates:

1. Make sure the name of the template is identical to the source template.

2. Copy the Nunjucks code exactly from one instance to the other, and test each template before saving it.

Recreate Actions

Similar to Shared actions above, recreating Scheduled actions and Event-based actions should be done one at a time, following the same recommendations:

1. Make sure the name of the Action is identical to the source instance.

2. Ensure that the schedule for the action, or the event that triggers it, is identical in the destination as configured in the source.

3. Copy every post function included in the Action in the same order they appear in the source instance.

4. Verify that the configuration of each post function in the destination is identical to the source.

Rebuilding workflows

Before adding extensions directly to workflows, you’ll need to either recreate your Workflows or migrate them to your destination instance. Once your workflows have been recreated in the destination, you can use the JMWE Workflow Extensions administration page to work through the list of extensions that exist on each workflow in your source. Go to Apps > Jira Misc Workflow Extensions and select JMWE workflow extensions in the right-hand panel.

Open each post function in your source by clicking its name and using the Workflow & Transition issue section, edit the appropriate workflow in your destination instance. Select the appropriate transition and add the extension type for the extension you are viewing (Post function, Condition, or Validator).