Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can i define the hierarchy under epic Edited

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



3 answers

2 accepted

2 votes
Answer accepted
Tarun Sapra Community Leader Apr 24, 2018

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.

@Tarun Sapra Thanks for the information but my client requesting the above flow.

0 votes
Answer accepted

No, Jira does not have sub-tasks of sub-tasks.

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?


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.

@Nic Brough _Adaptavist_ But how can i remove the Task from parent group, Could you please help me on this.

You rename it to something else.  Or delete it (and tell Jira what other types to swap the existing tasks to)

Hi @Suhas P

I can't define the hierarchy under Epic using Portfolio for JIRA, We can define the hierarchy above Epic.

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....

Suggest an answer

Log in or Sign up to answer
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

143 views 0 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you