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
One of the challenges working on JIRA is the lack of a three tier hierarchy ( EPICS -> Features -> User story) and hence reaching out to this group for further help.
My project is in need of 1-many relationship at each level ( one epic – multiple features, one feature – multiple stories) for effective release and backlog planning. As on today, JIRA supports a two tier hierarchy ( Epics -> features and Epic -> user stories) and that is not helping us break up business capabilities (From Roadmap) to Epics -> features -> user stories.
Can someone in this group please let me know if there are any solutions for this requirement.
Many people use Advanced Roadmaps to create issue types above Epics which helps them break down their work further.
We create a plugin called Agile Docs which lets you create levels of hierarchy both above and below Epics.
So you'll be able to configure an Epic -> Feature -> Story hierarchy in Agile Docs.
I recommend you add your Features to Epics using the "Epic Link" field and Stories to Features using the Agile Docs parent-child link to retain access to Jira's built-in Epic reports.