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

Issue Hierarchy

QQ Community:

When Creating a Hierarchy in Jira. Does Initiative Come First and Then Theme, Epic, Story or  does Theme come First then Initiative, Epic, Story?

I am getting Different Reponses  when Googling this. What is Best Practice?

 

Thanks

 

3 answers

3 accepted

2 votes
Answer accepted
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 25, 2022

@Tony B -

Welcome to the community.  As per other's responses, it is completely up to you.  You don't even have to use Initiative or Theme, you can name them to whatever it works for your organization.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

2 votes
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 25, 2022

Welcome to the Atlassian Community!

Technically, it's really up to you how you choose to implement your hierarchy

So, historically, Jira Software has implemented only three layers - Epic -> Issue -> Sub-task, and you can have many differently named issue types, and sub-tasks.  That obviously translates into Epic -> Story -> Sub-task in the names you are using.

Advanced Roadmaps gives you more flexibility - layers up above Epic.  The default is 

Initiative -> Theme -> Epic -> Story -> sub-task

But that's not fixed in stone, and the names are totally renamable.   Even their own docs do it differently (Odyddey -> Initiative -> Epic -> Story -> Sub-task).   I've seen initiative and theme reversed in that scheme in places, but what I see most often is something like 

Saga -> Epic -> Feature -> Story -> Sub-task   (People rename Epic to feature and then use Epic for the layer above)

The Epic -> Feature thing there is the (default) nomenclature for the Scaled Agile Framework, so we see it more often than other schemes.

TLDR: do what works best for you!

1 vote
Answer accepted
Robert Wen_ReleaseTEAM_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 25, 2022

Hello, @Tony B ! Welcome to the Atlassian Community!

I've seen Theme at the top, and then Initiative, Epic, etc. But honestly, there's no standard above Epic especially since Epics traditionally aren't time boxed the way stories are.

Hope this helps

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events