Re-migrating the same workflows after making changes in Datacenter

[Pierre Ibrahim]

Hello Atlassian community!

I need a sanity check, so I'm migrating a few hundred projects from DC to Cloud over phases, I'm planning to do the following:

Phase 1: Migrating 1 "cloned" project of every workflow scheme/workflow to Cloud so myself and my team can start configuring workflows early in Cloud. Those cloned projects will not have any tickets. I'm doing this solely to migrate shared project config as well as apps (JWT, JSU, and Scriptrunner)

Phase 2: Migrating about 400 projects with all tickets. Those projects would share the same as one of the cloned projects from phase 1 above:

• Workflow Scheme
• Screen Scheme
• Issue Type Scheme
• Priority Scheme
• Field Configuration Scheme

Timing here would be phase 1 in the next two weeks or so, and phase 2 would be a week or so before actual organization switch over to cloud to maintain ticket integrity.

My question here, since I'm not personally responsible for configuring all JIRA workflow schemes (My team and I are responsible for the bulk majority, but there's about 4 other workflow schemes that other teams are responsible for). If between phase 1 and 2 some of those workflows change, what's gonna happen when I do phase 2 of the migration?

I tested this with my sandbox instance in cloud, where I had already made changes to workflows migrated from DC, I then went to DC, cloned a project using the same workflow scheme in cloud, and migrated as is, nothing changed in cloud except adding the new project to a cloned workflow scheme (which honestly that would be great if this is what'll happen. My team and I want to have enough time to update the workflows in cloud, and don't want the original non cloud friendly workflows from DC to overwrite the changes we make in cloud).

Is this what's actually going to happen? Does anyone have experience doing something similar where you migrated just the "configuration" of your projects (by cloning), update your migrated workflows in cloud to make them cloud friendly, and then after some time migrate the actual projects utilizing the same named workflows?

[John Funk · Accepted solution]

Hi Pierre, 

That plan should work for the most part, however the problem will be with your tickets. If they are linked to a different workflow, there will have to be a migration of the tickets for statuses they are in right that do not exist in the new workflows. I am not sure if the migration tool will allow you/force you to do the migration of the tickets right then, of if they will auto migrate to other statuses. 

So, as a test, I suggest you do a cloned project with data right now. You can delete all of the tickets once they are created in the Cloud instance. 

[Pierre Ibrahim]

Thank you for your response, @John Funk ! Greatly appreciated.

That shouldn't be a problem as we're keeping the statuses the same across both DC and Cloud, we're merely just recreating the scriptrunner/JWT/JSU validators and post functions that don't seem to make it to cloud.

[John Funk]

Should not be a problem at all then.