Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 10, 2019

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
AUG Leaders

Atlassian Community Events