...
The JSU team is pleased to announce that JSU will be is compatible with Atlassian’s Jira Cloud Migration Assistant (JCMA) for app migrations. This means that for the first time, you’ll be able to you can automatically migrate most of your JSU workflow automations from your Server instance to your Cloud instance.
| Note |
|---|
It is highly recommended to test your migration on a different Cloud instance so that you may become familiar with the results, before proceeding to migrate your Server app data to your production Cloud instance. |
...
How to navigate to the Jira Cloud Migration Assistant add-on
| Info |
|---|
It is recommended to always use the latest available version of the Jira Cloud Migration Assistant (JCMA) add-on by Atlassian. As of writing the latest version is 1.6.3. You can track updates to JCMA through Atlassian’s app migration https://developer.atlassian. |
To begin preparing your instance for a migration to Jira Cloud, you first need to navigate to the “Migrate Migrate to Cloud”Cloud section within of the Jira administration settings. This can be found by going to:Settings/Cog Icon>>System>>Import and Export (side panel) - Migrate to cloud
...
Select Administration
> System.Under IMPORT AND EXPORT in the left sidebar, select Migrate to cloud. The Migration Assistant home page is displayed.
...
| Note |
|---|
Before you can commence a migration activity, you first need to go through complete the steps outlined in the JCMA tool in order to assess and prepare your apps. This guide will give a brief overview of how to do this with JSU. It is highly recommended to become familiar with Atlassian’s documentation on the topic https://support.atlassian.com/migration/docs/jira-cloud-migration-assistant/ while preparing your instance and other apps for a Cloud migration. |
...
How to include JSU in your app-assessment
Assess your apps - you will need to tell Jira select 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 status selected before you can proceed to the next step.
Select View app assessment.
Find JSU in the list of apps and
select Needed in Cloud from the Status dropdown.
When you’re happy to proceed,
select Done.
Prepare your apps - next, you now will need to link your Jira Cloud instance to the JCMA tool via on-screen prompts. Click “Choose cloud site” the prompts.
Select Begin preparing on the Prepare your apps panel on the Migration Assistant home page.
Select the required destination Cloud site then select Choose cloud site to link your chosen
cloud instance.
Select Continue to navigate through the remaining preparatory steps, then click Done.
Migrate your data - when ready, click “Create new migration”
When you are ready, on the Migrations Assistant home page, go to the Migrate your data paneland 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.
Select Connect to cloud.
Select the Choose what to migrate option.
Edit the options as required. For the Apps option, select All to ensure JSU is included in your migration activity.
...
Select Run pre-migration checks.
The migration assistant displays the results of all the pre-migration checks. Review any possible issues by expanding the relevant check.
Under Apps, select View app vendor checks.Status colour Purple title new
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.
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.
Select Continue to move to the Review stage of your migration, then when you are ready, select Runto commence your Cloud migration which includes your JSU app
...
data.
...
Reviewing the status of your migration
After commencing starting the migration activity, you can review it as it progresses by returning to Step 3 - “Migrate your data”the Migrations dashboard. Your Jira data will be migrated first, and then followed by your app data will be migrated afterward.
...
| Info |
|---|
You can click “View details” Click View details to see more information on the migration activity if desired. |
...
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 JSU Cloud Post-Migration Report”Report.
...
| Noteinfo |
|---|
The post-migration report will show a summary of “INCOMPLETE” if any warnings or errors were found during the migration. JSU relies on the JCMA tool to move across any workflows, resolutions, transitions etc. in order to configure your workflow rules correctly on your Cloud cloud site. |
...
Post
...
-migration report and cleanup
Click the link in the expanded section will to open up a new tab showing you with your post-migration report for this specific migration. You can To view any of your post-migration reports on your Cloud site by going to Settings/Cog Icon>>Apps>>cloud instance go to Settings Apps > JSU Automation Suite for Jira Workflows (side panel) - > Reporting.
...
| Info |
|---|
The examples on this page were created using our original beta Migration report. |
...
From January 2023 our Migration report contains additional details and features to make it easier for you to identify and resolve any problems with your workflows post-migration. You can see an example of the new report in our release documentation.
The report now includes:
The rule name, workflow, and transition with links to take you directly to the appropriate pages in your Jira instance.
Sortable columns to help you organize the issues in a way that suits you best
A Resolved checkbox to help you keep track of problems as they are fixed
Looking at the post-migration report, we can see there are 2 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 sidecloud instance. This specific scenario is likely to be caused by one of 3 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
| Info |
|---|
At this stage we can say that JSU has successfully performed an app-migration to the Cloud. All that remains is the specific clean up of workflow rules relating to any warnings identified |
...
Let’s look at the workflows 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 siteinstance.
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 errorIn 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.
As you might be able to see from the above images, our Our Cloud post - function is missing a value for the “Transition” field, whereas while the Server field contains the “Done” transition here.
If you remember our “The Missing transition” warning from the post-migration report, it also told us showed that a transition with ID “31” couldn’t be found. This is likely to be related to thatthe missing field, so let’s fix it. Let’s have a
First, look at the specific configuration of this post - function on our Server site vs Cloud sitethe Server instance compared to the Cloud instance.
Server:
...
Cloud:
...
On your Cloud sidecloud 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 by clicking “Update”.
...
...
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 using the options at the top of your screen.
...
…and that’s it! You’ve now successfully migrated to Cloud with all of your JSU workflow rules included!
...
...
Feedback wanted!
How did your migration go? Was this guide helpful? Still have questions?
Please feel free to contact us through our support channel and we’ll be happy to assist.