Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,369,734
Community Members
 
Community Events
168
Community Groups

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

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

Regards,
Earl

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
TAGS

Atlassian Community Events