Migrating project with an issue type between Epic and Story to Jira Cloud

[Tommy Heyser]

Is there any issue migrating from Jira Server/Data Center to Jira Cloud Standard a project with an issue level between Epic and Story?

Current project has a hierarchy Epic > Feature > Story > Sub-task.  Can it be migrated to Jira Cloud Standard with only Epic > Story > Sub-task ?

[Kelly Arrey]

Hi @Tommy Heyser , 

Another approach is to use the Structure by Tempo app to implement your Epic -> Feature -> Story -> Subtask issue hierarchy on Jira Cloud Standard.

We've defined a custom issue link type we call "contains <-> belongs to" - the parent issue "contains" the child issues - the child issues "belong to" the parent issue. Assuming the Jira Parent link data doesn't survive the migration, you'd have to create "contains <-> belongs to" links between all the relevant Features and Stories. There's some additional detail on how we put something like this together here and here if you're interested in finding out more.

Standard disclaimers apply: YMMV, deuces are wild, my only association with Structure by Tempo is that I'm a happy customer.

[Tommy Heyser]

@Kelly Arrey Thanks, Kelly.

[Alex Koxaras -Relational-]

Hi @Tommy Heyser and welcome to the community,

Are you using advanced roadmaps on server/DC? If you are migrating to Standard cloud plan, which doesn't include advanced roadmaps, then this hierarchy will be lost. You'll have your issue types alright, but not the hierarchy. I would see two possible solutions:

1. Change everything on your server/DC instance and then migrate (preferrable)
2. Get a trial premium plan for cloud, migrate and then do all the changes quickly. After that downgrade to standard

Imo, I would go with option no 1, since Atlassian also favorites a good cleanup before moving to cloud.

[Tommy Heyser]

When you say "change everything", do you mean:

1) putting the issue type(s) associated with the "feature" hierarchy level at the "story" level (level 0), and

2) make the Epic issue type an "epic" level (level 1)?

[Alex Koxaras -Relational-]

@Tommy Heyser yes, I mean that you should "map" your server issue types to what will be valid on cloud. E.g. on JSW cloud you have out of the box the hierarchy:

Epic > Standard Issue type > Subtask issue type

[Tommy Heyser]

@Alex Koxaras -Relational- thanks, we'll look into this.