The JSU team is pleased to announce that JSU will be compatible with Atlassian’s Jira Cloud Migration Assistant (JCMA) for performing app-migrations. This means that for the first time ever, you’ll be able to automatically migrate most of your JSU workflow automations from your Server instance to your Cloud instance.

How to navigate to the Jira Cloud Migration Assistant add-on

To begin preparing your instance for a migration to Jira Cloud, you first need to navigate to the “Migrate to Cloud” section within the Jira administration settings. This can be found by going to:

Settings/Cog Icon >> System >> Import and Export (side panel) - Migrate to cloud

How to include JSU in your app-assessment

1. Assess your apps - you will need to tell Jira which apps you want to include in your migration. All apps must have a decision made for them before the tool will allow you to proceed to the next step.
   
   Find JSU in the list of apps and mark this as “Needed in Cloud”.
   
   When you’re happy to proceed, click “Done”.
   

   

   
   

2. Prepare your apps - you now will need to link your Jira Cloud instance to the JCMA tool via on on-screen prompts. Click “Choose cloud site” and proceed to link your chosen Cloud instance and navigate through the remaining preparatory steps.
   
   

   

   
   

3. Migrate your data - when you’re ready, you can click “Create new migration” to begin your migration activity. Proceed through the on-screen prompts until you are ready to commence the migration.
   

   

   

Reviewing the status of your migration

After commencing the migration activity, you can review it as it progresses by returning to Step 3 - “Migrate your data”. Your Jira data will be migrated first, and then app-data will be migrated afterwards.

The app-migration stage is the last step of the migration activity. When this stage has completed you can expand to see more information, including a link to the “JSU Cloud Post-Migration Report”.

Post Migration Report and Cleanup

Clicking the link in the expanded section will open up a new tab showing you your post-migration report for this specific migration. You can view any of your post-migration reports on your Cloud site by going to

Settings/Cog Icon >> Apps >> JSU Automation Suite for Jira Workflows (side panel) - Reporting

Looking at the post-migration report, we can see there are 2 warnings reported - one “Missing resolution” and one “Missing transition”.

These are because JSU couldn’t find a specific resolution and transition it needed to configure some features correctly on the Cloud side. This specific scenario is likely to be caused by one of 3 scenarios:

• The JCMA tool didn’t migrate those specific resolution and transitions for unknown reasons

• The JCMA tool didn’t migrate those specific resolution and transitions because they already exist on the Cloud site but with different IDs

• The JCMA tool migrated those specific resolution and transitions but in doing so gave them new IDs which don’t match the Server configuration

Let’s look now at the workflows rules side-by-side on both platforms - how they are originally on our Server instance, and how they look after being migrated to the Cloud site.

Server:

Our server workflow contains 3 JSU post-functions, one of each for Linked Transition, one Clear Field Value and Update Any issue Field

Cloud:

All 3 have been successfully migrated to the Cloud, but the Linked Transition has a visible error

In the above images, you can see that all of our JSU post-functions have been successfully migrated to our Cloud site, but we can see the Linked Transition has a visible error. To deduce why that is we can have a look at the specific configuration of this on our Server site vis Cloud site.

Server:

Cloud:

As you might be able to see from the above images, our Cloud post-function is missing a value for the “All other sibling issues (for example linking to the target with the same link type) must have one of the following statuses” field, whereas the Server field contains the “Done” transition that has an ID of “31”.

If you remember our “Missing transition” warning from the post-migration report, it also told us that a transition with ID “31” couldn’t be found. Now that we’ve found the misconfiguration, let’s fix it.

On your Cloud side, edit the misconfigured post-function and add the correct transition to the empty field value (in our case we need to add “Done”) and then save your changes by clicking “Update”.

After you’ve resolved all issues on a workflow, don’t forget to Publish your workflow using the options at the top of your workflow screen.

…and that’s it! You’ve now successfully migrated to Cloud with all of your JSU workflow rules included! 🎉