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

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,457,352
Community Members
 
Community Events
176
Community Groups

Creating a custom Hierarchy

We're trying to create a couple of custom hierarchies to better manage EPICs and Tasks.

It could be a visual Hierarchy - as in we specify the grouping for the display - or an actual Hierarchy enforced in the workflow. I suspect that a visual Hierarchy is the more llikely.

Essentially we'd like to be able to support these two concurrently:-

  • 1) EPIC -> Tasks -> Sub-Tasks (eminently doable as standard)

  • 2) EPIC -> User-Story -> Tasks -> Sub-Tasks (don't know how to achieve this)

The problem is that User-Story & Tasks are at the same level (both a child of an EPIC), so when you are in an EPIC view, both User-Story & Tasks are lumped together under the EPIC and you cannot see how what User Story/Task links exist without going into the item, which is a royal pain.

1 answer

1 accepted

1 vote
Answer accepted

Welcome to the Atlassian Community!

In Jira Premium, you have access to Advanced Roadmaps, in which you can set up a hierarchy above Epic, and set up other levels.

You can't do two conflicting schemes at the same time, that makes no sense, whatever the software, and it is not helpful for humans to see hierarchies that skip layers (although you can partly do it in Jira - Epics can have sub-tasks without needing an issue in-between them because the Epic is a type of issue, despite being in the layer above issues)

So, in Advanced Roadmaps, I would set up

  • Epic
    • User Story
      • Task
        • Sub-task

But not as a simple add.  I would rename Epic as "user story" first, then add a new issue type for Epic and promote it above the "new" user story.  I think I would add other issue types at the task and sub-task levels, and possibly others at user-story level and maybe Epic too.

Or, you could set up 

  • Epic
    • User Story
    • Task
      • Sub-task

if you wanted to keep user-story and task as issue types at the same level

Thanks so much for this. Extremely helpful.

Like Nic Brough -Adaptavist- likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS

Atlassian Community Events