Migration support for custom issue type hierarchies created in Advanced Roadmaps

[David Holman]

I'm getting ready to migrate an acquired company's Jira and Confluence into the acquirer's instance. 

The source instance has Advanced Roadmaps installed but the destination instance does not.

In the source instance a custom initiative issue type was created and the hierarchy level was set above Epic in the AR add-on. 

Does anyone know if/how this will migrate to the destination account without the AR add-on? Is there anything I can do to ensure the structure is retained?

[Trudy Claspill · Accepted solution]

Hello @David Holman 

Is this a self-hosted to self-hosted, self-hosted to Cloud migration, or Cloud to Cloud?

I don't know it for a fact, but my theory is that if the destination environment doesn't have AR then while the issue type might be retained the structure cannot be retained. Without AR there is no way to visualize the hierarchy. Without AR you can't edit the Issue Type Hierarchy to add levels above Epics.

[David Holman]

It's Cloud to Cloud.

As far as the set up and "dry run" functionality goes, it's been really smooth. I'm just surprised nothing in the process highlighted the fact that the destination account is a step down -- seems like a good point to upsell 🤑

[David Holman]

Actually, it appears that vanilla Jira now has a default Initiative issue type that contains Epics. I should be able to map my source issues to that type in and have the destination reflect the hierarchy I'd expect … right?

I'll report back once I get on the other side of the migration. I'm sorting out other concerns right now.

[Trudy Claspill]

Is the subscription for the destination site/product Premium or Enterprise? If so, then AR is automatically available. 

If the destination site is using a Standard subscription, then the issue hierarchy can't be extended with native functionality. There may be an Initiative issue type in the destination site, but without AR there is not native support for recognizing the additional parent/child relationship.

[David Holman]

No, that's exactly the issue I'm asking about. The source subscription in Premium, the destination is not.

But, as stated above, I think I've solved it. I won't find out until I do a test. I can't do that until we finish dealing with user conflicts. But I will report back on whether my simple issue type rename solved it.

[David Holman]

The issue type ("Initiative") came across, but it lost the link to all of it's epics.

There is no way the org is going to pay for Premium on ~100 users just to have a basic three-tier issue hierarchy. Everything we found during this migration only reduced the org's confidence in Jira. Really disappointing overall.

[David Holman]

I should note how I solved this stupid limitation: labels. I just used a label to hold the initiative together 😒

[Lauren Hinrichs]

Yikes.