nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Downgrading Premium to Standard

kenneth.muylaert

Hello, we are looking into downgrading our Jira license.

We are currently using Advanced roadmaps to create issue types above Epics with the hierarchy feature. We currently have epics linked in a child relation with another issue type.

My question is: will we lose the links (parent child) after the downgrade? what will happen to our workitems created above the epic level - will they become an epic?

To give an example: we created portfolio epic (parent 1) above epic (child 1) and have some issues as portfolio epic, what type of work item will these get after the downgrade? And what will happen to the parent child relation?

Comments

Mark Davies_abjjxh

Hi @kenneth.muylaert

Issue types that were configured above (or on the same level as) the epic level will remain in place. You won't lose any issue relationship data upon downgrading.

You would lose access to Advanced Roadmaps, which is the only experience in Jira that makes use of hierarchy above epic. Everywhere else in Jira would treat these issue types as standard issue types.

kenneth.muylaert

So our portfolio epics/features that we made in a hierarchy above epic user story and task will remain in place when downgrading? and we would keep parent child relationships?

Mark Davies_abjjxh

Yes, that's correct. The relationship data and hierarchy mappings are untouched, as some customers may wish to re-upgrade and make use of their existing configuration.

Just keep in mind that when downgrading, you would no longer be able to make use of the hierarchy above epic.

For example, you would no longer be able to add child issues to any new or existing issues that sit above the epic level. You would also not be able to set a parent issue for any new or existing issues that sit on the epic level, as these experiences are only supported in Advanced Roadmaps.

Dave Rosenlund (Trundl)

Hi, @kenneth.muylaert. Welcome to the community!

First, can you confirm that we're talking about Atlassian Cloud here? (It's certainly implied, but it's always best to be sure.)

Second, while I am certain everything @Mark Davies says is absolutely correct, the thing that is missing from this discussion is anything about the use of 3rd-party apps from the Atlassian Marketplace.

There are a number of apps that will enable you to work with custom, deeper, hierarchies created inside or outside of Advanced Roadmaps. And, they are typically more cost-effective than a Jira Cloud premium or enterprise subscription (this is where that confirming question above comes in) because they can be used on the sub-premium (or enterprise) plans.

In my experience, the two that are the most popular — and that provide features akin to what you had in Advanced Roadmaps, are Structure/Structure.Gantt and/or BigPicture/BigGantt.

But they are not the only ones. You can search the Atlassian Marketplace for things that best suit your needs. For example (the cloud assumption comes into play here again):

https://marketplace.atlassian.com/addons/app/jira/top-selling?hosting=cloud&query=hierarchy

Hope this helps,

-dave

P.S. Full disclosure: I work for the company that makes Structure.

Walter Lee_thsywb

I understand not performing actions on the objects above EPIC level. What about READ rights of those objects so we can view the historical context of the data. When downgraded to the standard plan, can you query those objects to read them even?