Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,298,327
Community Members
 
Community Events
165
Community Groups

Advanced Roadmaps Hierarchy Configuration

Edited

I have a pretty specific question that I'm hoping someone with advanced Portfolio (Advanced Roadmaps) knowledge can help me with.  When my company implemented Portfolio in 2017, we added a hierarchy level and issue type called Feature, and somehow got it to be between the Epic and Story level, which is what we wanted.  This caused Feature issue types to show up in the Epics panel of the backlog view in Jira, which was also what we wanted at the time.

We are now looking to restore the default hierarchy, so that Epics back to being are the parent issue types of Stories, but I'm unable to remove the configuration we added originally. 

How can I undo what we did and restore default functionality of Jira?? 

Portfolio Config.jpg

3 answers

Hi @Jovanna Pugh 

I have been trying to achieve exactly what you did above. I am wanting to add Feature under Epic. I would like the hierarchy to be Epic > Feature >Story but I just can not see where to do this. If you would so kind as to let me know how you did this, I would really appreciate it.

Many thanks

Hello @Jovanna Pugh , that's an interesting, issue. I know that you cannot remove epics, stories, and sub-tasks, since these comprise the default hierarchy level in Advanced Roadmaps. I am trying to understand why isn't the "Feature" level showing as custom level in your hierarchy. I don't think reinstalling plugin would change your hierarchy to default. But, you can try changing the "Jira Issue Type" for "Feature" level and see if it changes anything regards to "remove". Also, please go through some of the comments from atlassian team member on this post, it will help you understand about some of the impacts of hierarchy removal Advanced-Roadmaps Impact of hierarchy removal

@Sachin thank you, that post looks very helpful!

Like Nicolas Grossi likes this

Try creating a new instance of Jira (from scratch) with the plugin/add on installed (from scratch) too and then import the projects 1 by one.

Thanks @Nicolas Grossi - I was hoping not to have to go that drastic, but I will keep this in mind!

Like Nicolas Grossi likes this

For me is the correct solution based on your needs. Drastic is only a way of thinking.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

179 views 1 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you