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

Jira Cloud: Problem with Subordinated Issues

Hello Community, 

we have arranged a new issue hierarchy, which looks like this: 

 

Initiative          hierarchy level: 3

Theme             hierarchy level: 2

Epic                 hierarchy level: 1

Briefing           hierarchy level: 0

Bug                 hierarchy level: 0

Story               hierarchy level: 0

Task                 hierarchy level: 0

Subtask           hierarchy level: -1

 

Now we noticed, that when you try to create subordinated issues within an epic, you have the possibility to create an initiative or a theme, which shouldn't be possible, as initiative and theme are above epic in the hierarchy level:Bildschirmfoto 2023-09-27 um 14.38.19.pngIt should only be possible to create a story. How can we fix this? 

Thank you!
Nicole 

 

1 answer

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 27, 2023

Hello @Nicole Zimmermann 

That is not an issue that can be fixed at this time.

While those issue types are above Epic in the hierarchy, that portion of the hierarchy is respected only when you are using Advanced Roadmaps Plans and directly modifying a Parent field.

Those additional issue types are still considered "standard" issue types otherwise and as such will appear in the Child Issues options under Epics.

I've been looking for a change request about this in Atlassian's public backlog but have not yet found one.

Thank you Trudy! 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events