You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
You would need a plugin, which would let you to show your issues as a hierarchy. For example, you could use the Structure plugin:
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!
Hi @Igor Sereda [ALM Works] - I plan to use issue link to establish Component -> Epic -> Feature -> User Story -> Task hierarchy. In order to do this, should I be creating "relates to" link from epic to feature and then open feature tickets and again create "relates to" links to user story and then open user story tickets and create "relates to" link to tasks ?
Does it matter from which issue type ticket I create the "relates to" link ?
I am currently using the below structure automation to display the hierarchy - what are your thoughts on below? is this the most efficient way ? can this be optimized?
Note: Component 1 and 2 is dummy data that is not required in the structure.
David from ALM Works here!
The direction of the link will matter, as well as the issues you are linking.
The "relates to" link would not initially be ideal, since both directions are listed as "relates to". This can cause some confusion when building your hierarchy (and in general).
You can rename the outward and inward text to make it clear which direction the link points. You could also create a new issue link and customize it to your needs.
You will want to establish the links as you mention "Component -> Epic -> Feature -> User Story -> Task".
The structure you picture is very well crafted!
Please let us know if you have any additional questions! The support team can be reached via email@example.com
I would like to know if 'Jira Software Cloud Standard' edition today in late 2023 supports this level of structure out of the box?
- Namely: Epic > Features > Story
If not, is Structure by Tempo - Jira Portfolio Management & PPM | Atlassian Marketplace my only option?
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!