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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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
Hello @sudheer
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, Jira does not have sub-tasks of sub-tasks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My qsn is under Epic i want to create Feature and under Feature i want to create Story and for that story i want to create Task. Is it possible?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes.
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 must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- But how can i remove the Task from parent group, Could you please help me on this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You rename it to something else. Or delete it (and tell Jira what other types to swap the existing tasks to)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can have a look at Structure for JIRA
https://marketplace.atlassian.com/plugins/com.almworks.jira.structure/server/overview
Also Portfolio for Jira can also help
https://marketplace.atlassian.com/plugins/com.radiantminds.roadmaps-jira/cloud/overview
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Suhas P
I can't define the hierarchy under Epic using Portfolio for JIRA, We can define the hierarchy above Epic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I wonder why Atlassian is sticking to a fixed hierarchy epic-user story -task? It's not agile at all to do so but more just annoying. With other issue management systems, you set up in seconds any hierarchy you want....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.