Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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
Community Members
Community Events
Community Groups

Three Tier Hierarchy (Epics-> Features-> user stories) in JIRA

Hello Everyone, 

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. 


Bunty Parekh

1 answer

Hi @Bunty Parekh 

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.

Best Regards,


Suggest an answer

Log in or Sign up to answer