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
Can i define the hierarchy under epic?
Currently i can manage Business Requirement->Epic->Feature/Story->Sub-task But i need the hierarchy like Business Requirement->Epic->Feature->Story->Task/Sub-Task
You can have the hierarchy you want, using the "Issue linking" feature. From your hierarchy it seems that you are trying to implement the "SAFe" framework in JIRA which is fine as well but I personally recommend to stick to "Epic<->Story" hierarchy in JIRA because it's so tightly coupled in JIRA.
So when you move the Epic an level up and have the hierarchy Epic -> Feature -> Story then you loose the Epic<->Story coupling which will lead to confusion once you start using the system at a larger scale. Because you have fields like Epic Name, Epic Link and on boards it's Epic Panel and in plugins like SR there are JQL functions like "issuesInEpic" etc
So there is a tradeoff when going forward with this approach. My preferred hierarchy is
"Initiative -> Epic -> Story -> Sub-Task" , it works well with JIRA and with plugins.
No, Jira does not have sub-tasks of sub-tasks.
Assuming you have a default Jira, you already have an issue type called task, and it's a parent level one. You will need to rename that to something else, then you will be able to create "task" as a sub-task type and use it beneath Stories.
You rename it to something else. Or delete it (and tell Jira what other types to swap the existing tasks to)
You can have a look at Structure for JIRA
Also Portfolio for Jira can also help