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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Why does custom hierarchy issue display in plan sprint capacity

Why does custom hierarchy issue display in plan sprint capacity and is also alert that issue is not assigned to sprint?  Issue TTEG-12 OKR 1 is showing on the sprint capacity with 0 days even though it is a parent issue to the Epic.  Did I miss a setting somewhere for the custom hierarchy?


1 answer

1 accepted

0 votes
Answer accepted
Ismael Jimoh Community Leader Feb 09, 2022

@Tracy Stimac fundamentally Roadmap and your JIRA Software board are 2 different things.

For the standard JIRA software board, irrespective of what hierarchy you set, Epics are the highest issues. Whereas with the Plan under Advanced Road Maps, this can be reconfigured.

Hence as far as I know, what you see is the expected behaviour for each of the views you are seeing.


This may be expected behavior but I'm not thrilled that our highest level hierarch is showing in the sprint capacity view.  May need to submit an enhancement request on this one.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events