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

[Bernd Anderer]

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

[Earl McCutcheon]

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:

• Configuring initiatives and other hierarchy levels

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

[Bernd Anderer]

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