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
In order to properly breakdown and categorize work, our team would like to use a higher level issue type, such as Business Increment (BI). This would contain multiple epics which would in turn would contain multiple stories. I'm trying to understand how we could link epics to BIs in much the same way we link stories to epics. Our overall solution would include a three tiered structure where each tier could link to the one above it. Has anyone successfully implemented something similar on JIRA server?
What we've done so far:
We've tried to utilize sub-tasks/stories/epics, however the limitations on this include an inability to visualize sub-tasks on JIRA board and backlog the same way we currently view stories.
Hi, @Josh. Welcome to the community.
Your question is frequently asked — the community is packed full of threads about Jira's out-of-box 3-level hierarchy. Please forgive me for skipping ahead to the "answer."
To achieve what you describe, you will need a Jira add-on. Since you are on Jira server (according to the tags on this post), you must choose an Atlassian Marketplace app.
On Data Center or Cloud, Atlassian's Advanced Roadmaps would be another choice — but it's not available for Sever.
But you can also conduct your own marketplace search — for example:
Best of luck to you — I hope this helps,
Unfortunately, nothing yet and IMHO it is unlikely to change. But that’s just my opinion. 😊