Jira Cloud Migration Assistant (JCMA)

JSU is compatible with Atlassian’s Jira Cloud Migration Assistant (JCMA) for app migrations. This means you are able to automatically migrate most of your JSU workflow automations from your Server/Data Center 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 of the Jira administration settings.

1. Select Administration > System.

2. Under IMPORT AND EXPORT in the left sidebar, select Migrate to cloud. The Migration Assistant home page is displayed.

Open

How to include JSU in your app assessment

1. Assess your apps - you will need to select which apps you want to include in your migration. All apps must have a decision status selected before you can proceed to the next step.
   
   Find JSU in the list of apps and select Needed in Cloud from the Status dropdown.
   When you’re happy to proceed, select Done.
   
   

   Open

   

    

2. Prepare your apps - next, you need to link your Jira Cloud instance to the JCMA tool via the prompts. Select Choose cloud site to link your chosen cloud instance and navigate through the remaining preparatory steps, then click Done.
   
   

   Open

   

    

3. Migrate your data - when you are ready, on the Migrations dashboard, select Create new migration to begin your migration activity. Proceed through the corresponding prompts until you are ready to commence the migration.
   
   

   Open

   

   
   
   

   Open

   

   1. On the step “Would you like to migrate your Apps?” - Select All to ensure JSU is included in your migration activity.

   2. Review any possible errors relating to your migration before proceeding. Click Run to commence your Cloud migration which includes your JSU app data.

Reviewing the status of your migration

After starting the migration, you can review it as it progresses by returning to the Migrations dashboard in step 3. Your Jira data will be migrated first, followed by your app data.

Open

Open

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

Open

Post-migration report and cleanup

Click the link in the expanded section to open a new tab with your post-migration report for this specific migration. To view any of your post-migration reports on your cloud instance go to Settings Apps > JSU Automation Suite for Jira Workflows > Reporting.

Open

Open

Looking at the post-migration report, we can see there are two 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 instance. This specific scenario is likely to be caused by one of three scenarios:

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

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

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

Let’s look at the workflow 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 instance.

Server

Open

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

Cloud

Open

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

Our Cloud post function is missing a value for the Transition field, while the Server field contains the “Done” transition.

The Missing transition warning from the post-migration report, showed that a transition with ID “31” couldn’t be found. This is likely the missing field, so let’s fix it.

First, look at the specific configuration of this post function on the Server instance compared to the Cloud instance.

Server

Open

Cloud

Open

On your cloud instance, edit the misconfigured post function and ensure the correct values are added to the Transition values (in our case the same workflow with transition “Done” and ID “31”) and then click Update to save your changes.

Open

After updating the post function, the error no longer appears. After you’ve resolved all issues on your workflow, don’t forget to publish your workflow.

Open

You’ve now successfully migrated to Cloud with all of your JSU workflow rules included!