...
| 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 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” to begin your migration activity. Proceed through the on-screen prompts until you are ready to commence the migration.
...
| 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, schemes, resolutions, transitions etc. in order to configure your workflow rules correctly on your Cloud site. |
...
Our server workflow contains 3 JSU post-functions, one of each for Linked Transition, one Clear Field Value and Update Any issue Field
...
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 statusesTransition” field, whereas the Server field contains the “Done” transition that has an ID of “31”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. Now that we’ve found the misconfiguration, let’s fix it.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 add ensure the correct transition values are added to the empty field value “Transition” values (in our case we need to add “Done”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 a your workflow, don’t forget to Publish 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! 🎉
...