Migrating with the Jira Cloud Migration Assistant (JCMA)

The JSU team is pleased to announce that JSU is compatible with Atlassian’s Jira Cloud Migration Assistant (JCMA) for app migrations. This means that you can 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 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.

   1. Select View app assessment.

   2. Find JSU in the list of apps and select Needed in Cloud from the Status dropdown.

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

   1. Select Begin preparing on the Prepare your apps panel on the Migration Assistant home page.

   2. Select the required destination Cloud site then select Choose cloud site to link your chosen cloud instance.

   3. Select Continue to navigate through the remaining preparatory steps, then click Done.
      
      

       

3. Migrate your data

   1. When you are ready, on the Migrations Assistant home page, go to the Migrate your data panel and select Create a migration to begin your migration activity. If you have already performed a migration, you can select Create a migration on the Migrations dashboard page.

   2. Select Connect to cloud.
      
      

       

   3. Select the Choose what to migrate option.

   4. Edit the options as required. For the Apps option, select All to ensure JSU is included in your migration activity.
      
      

   5. Select Run pre-migration checks.

   6. The migration assistant displays the results of all the pre-migration checks. Review any possible issues by expanding the relevant check.
      
      

   7. new Under Apps, select View app vendor checks.
      JSU has implemented two app vendor checks to help your JSU data migrations run smoothly. See https://support.atlassian.com/migration/docs/app-vendor-checks/ to learn more about app vendor checks.
      
      

   8. Follow the steps to resolve any issues before proceeding, or download a report to help with post-migration cleanup as described in the next sections.
      
      

       

   9. Select Continue to move to the Review stage of your migration, then when you are ready, select 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. Your Jira data will be migrated first, followed by your app data.

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.

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.

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 that specific resolution and transition for unknown reasons

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

• The JCMA tool migrated that specific resolution and transition 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

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

Cloud

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

Cloud

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.

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.

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