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

Portfolio for Jira 3.5: Why is there no TASK in between Story -> Sub-Task?

The default hierachie in Portfolio is EPIC-> STORY -> SUB-Task

I know how to add additional levels.

Why did Atlassian do it that way? Why is there no TASK level between STORY->TASK?

Why can I not add that level, so that I have

EPIC -> STORY ->TASK -> Sub-Task?

Any idea?

Thanks in advance

1 answer

1 accepted

0 votes
Answer accepted

Hi Bernd,

The Hierarchy path of EPIC-> STORY -> SUB-Task is a set and default hierarchy path configuration defined by Jira and cannot be changed without add-ons.  You can add in levels above the Epic called Initiatives, additional details on the default levels and Inatitive configuration ca be seen here:

To rearrange the default configuration, the App Structure allows for this, and I would recomend checking it out to see if it fits your needs.


Thank you for your answer. I guess I have to accept this then :-) 

Like Earl McCutcheon likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Advanced Roadmaps

3 short videos to help you get started with Advanced Roadmaps

Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...

3,469 views 22 15
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