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; } } }

Epic Feature Story Hierarchy?

Khadhar Mohaideen

I have a requirement where we want to introduce Features as an issue type with the hierarchy of Epic --> Feature ---> Story ---> Sub-tasks., where we should be able to link Features as children of Epic and Stories as children of Features (with a filed similar to "Epic Link", such as "Feature Link" which links Features to Stories).

I don't want to rename Epic. Please let me know if this is possible in Jira.

Accepted answers

Alexey Matveev

Hello,

You would need a plugin, which would let you to show your issues as a hierarchy. For example, you could use the Structure plugin:

https://marketplace.atlassian.com/apps/34717/structure-for-jira-projects-at-scale?hosting=server&tab=overview

All comments

Alexey Matveev

Hello,

You would need a plugin, which would let you to show your issues as a hierarchy. For example, you could use the Structure plugin:

https://marketplace.atlassian.com/apps/34717/structure-for-jira-projects-at-scale?hosting=server&tab=overview

Khadhar Mohaideen

Thank you Alexey.. I suppose this the same functionality as provided by Jira Portfolio plug-in..

Igor Sereda [ALM Works]

With Portfolio, I don't think you can "insert" Feature level between Epics and Stories (without renaming Epics to become "Features"). Additional levels can be added above Epics.

Also, in Portfolio the levels are configured globally for the whole instance.

(But sometimes that's sufficient and people do rename Epics.)

Structure has a different approach – with hierarchies configurable per structure and basically the way you want. You'll need to use issue links though to represent the relationships Epic-Feature and Feature-Story. (Alternatively, you can just manage the hierarchically manually in Structure, without representing it with Jira data.)

Hope this helps!

Igor

Khadhar Mohaideen

Thank you Igor. That's really helpful ...!

Bryan McMillan_4pe0cs

Khadhar,

You can acquire the SAFe Epic to Feature Translation https://marketplace.atlassian.com/apps/1218959/safe-epic-to-feature-translator-for-jira?hosting=server&tab=pricing,

which will update all of the places in Jira with the word "Feature" where the word Epic now shows up. And you don't need to necessarily be doing Scaled Agile Framework to us it. All of the characteristics you are used to using Epics will now be Feature Name, Feature Link, Feature Color, etc. Jira will use Features in place of Epics once installed. So, you then go create an Issue called Epic, which will then be just like any other Issue in Jira (i.e., just like Story, Spike, Bug, etc.) and link those to your Feature Issues. Portfolio will need to have it's hierarchy updated to accommodate the change. I have installed this Add-On a good number of times and it works without problems or issues. It might take some training of your end-users to understand that it is now a Feature in place of the Epic and if you create an Epic to be higher in the hierarchy they'll need to understand that. Features will have children Stories and Stories will have Sub-Tasks. If you do create another new Epic Issue Type then Epics will have Linked Features using the Issue Link.

Hope this helps!

Bryan

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira