Issues during Migrating Jira Server to the Cloud: Workflow, Media

[Mykola Pronkin]

We have a fairly large instance on the Jira server. It includes a number of projects, many custom workflows, fields, transitions, and a large amount of media materials.
We are exploring the possibilities of migrating our data from the server to the cloud. We launched a test Jira server, filled it with tasks similar to ours, fields, workflows, media, and attempted to migrate it to a cloud instance using the Jira Cloud Migration Assistant.

We made several attempts, but encountered the same issues in each of them:

1. Post-functions built on scripts (Adaptivist script runner) are not preserved in the workflow in migrated Jira.
2. Adding comments to an issue during a transition is not working.
3. Transition conditions are not being properly checked.
4. We are experiencing significant issues with media files, as the image names are mixed up. Consequently, in the migrated Jira, the images do not correspond to the tasks they should be associated with. Some images appear in the descriptions, while others do not.

Would be very grateful for any hints, solutions, or advices!

[Brant Schroeder · Accepted solution]

@Mykola Pronkin were you able to get this resolved? 

[Mykola Pronkin]

@Brant Schroeder actually no. Received another priorities.

[Brant Schroeder]

@Mykola Pronkin When you start working on it again here are my recommendations.  

1. Post-functions built on scripts (Adaptivist script runner) are not preserved in the workflow in migrated Jira. - Review their migration document.  Not all features migrate and you can use this to identify which ones and come up with a new solutions and document that so it can be implemented in the cloud. https://docs.adaptavist.com/sr4js/latest/scriptrunner-migration/migrating-to-or-from-cloud/migrate-from-scriptrunner-for-jira-server-to-cloud  Submit a support issue with Adaptivist if you get stuck.
2. Adding comments to an issue during a transition is not working. Depending on how you implemented this (if you used an app) you might have to add a screen on the transition again. (Company Managed Project)  https://confluence.atlassian.com/jirakb/map-a-screen-to-a-workflow-transition-in-jira-company-managed-projects-720634253.html  You will need to document which workflows need it and then make the adjustment after your migration.
3. Transition conditions are not being properly checked. These might have to be added again as well depending on what condition you had in server.  https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/ 
4. We are experiencing significant issues with media files, as the image names are mixed up. Consequently, in the migrated Jira, the images do not correspond to the tasks they should be associated with. Some images appear in the descriptions, while others do not.  This is an odd one and I am not sure why that would happen.  I am not aware of any issues like this.  I would suggest working with Atlassian support to see if they can take a look at your cloud instance and see why this occurred.

[Brant Schroeder]

@Mykola Pronkin Can you accept this answer to help others?

[Mykola Pronkin]

Hey @Brant Schroeder accepted, could add from my side:
1. Old staff that was performed by post-functions on script runner could be covered by Jira cloud scenarios. It less clear and require bigger construction - but it works.
2. Solved by scenarios too.
3. Solved by scenarios too.
4. Unresolved, had a session with Jira support. They dug, but problem still exist.