| Info |
|---|
This information is correct as of October November 2021 |
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.
| Note |
|---|
Please note, app-compatibility with JCMA is still considered as in beta. JSU is offering our customers and partners early-access to the functionality and so that we may get feedback on the migration experience by participating customers. This means that while we strive for functionality that works 100% as intended, there may be undiscovered issues as we test and improve the compatibility. Additionally, due to some feature differences between JSU Server and JSU Cloud, not all features can be migrated at this time. It is highly recommended to first 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. |
...
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:
...
| Note |
|---|
Before you can commence a migration activity, you first need to go through 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 recommend recommended to become familiar with Atlassian’s own documentation on the topic while preparing your instance and other apps for a Cloud migration. |
...
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”.
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.
Migrate your data - when you’re ready, you can click “Create new migration” migration” to begin your migration activity. Proceed through the on-screen prompts until you are ready to commence the migraitonmigration.
...
| Note |
|---|
IMPORTANT: On the step “Would you like to migrate your Apps?” - Ensure “All” is selected to ensure JSU is included in your migration activity. |
...
| Note |
|---|
IMPORTANT: 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 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.
...
| Info |
|---|
Hint: You can 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 completed you can expand to see more information, including a link to the “JSU Cloud Post-Migration Report”.
...
| Note |
|---|
Note: 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 site. |
...
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
| 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 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, 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.
As you might be able to see from the above images, our Cloud post-function is missing a value for the “Transition” field, whereas the Server field contains the “Done” transition here.
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. This is likely to be related to that, so let’s fix it. Let’s have a look at the specific configuration of this post-function on our Server site vs Cloud site.
Server:
...
Cloud:
...
On your Cloud side, 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 save your changes by clicking “Update”.
...
As you can see in the above image, 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! 🎉
...
| Tip |
|---|
Feedback wanted! How did your migration go? Was this guide helpful? Still have questions? Please feel free to contact us through our usual support channels and we’ll be happy to assist. |