Advanced Roadmaps Hierarchy Configuration Edited

[Jovanna Pugh]

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?? 

[Nicolas Grossi]

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.

[Jovanna Pugh]

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

[Nicolas Grossi]

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

[Sachin]

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

[Jovanna Pugh]

@Sachin thank you, that post looks very helpful!

[Sachin]

Your welcome @Jovanna Pugh !