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!


Why don't I get overbooked capacity in red?

So, basically, in the documentation, I found something like this:


when I look at my schedule, I also have releases with a fixed release date, but I don't get the red indicator which should tell me how much I'm overbooked. I only get the "bottleneck" info. While my release is overbooked. For some reason he just schedules it over the fixed release date, instead of trying to put everything IN the release and then saying "person X is overbook by Y days"


2 answers


I disn't wanted to add a new topic for the same question, so:

I have the same problem.

Here is what I have:

1 Portfolio plan with 1 project and 1 team. the team is overbooked for the releases for sure. But instead of showing the overbooked hours on the bars, the release finish date is moved to a later date.
I understand, that this is caused because of the grouping, but no grouping is selected, see :JIRA portfolio.jpg

What can be the reason?

Thank you, br


The situation in which the overbooked bar is not showing is when the capacity view is grouped by project. With that option on show neither free capacities nor overbooked capacities but just the workload assigned to that sprint. The reason for that is that when the view is grouped by projects, it is not clear to which project the free sprint capacity / overbooked sprint capacity should contribute so we'd need to distribute it following some heuristic which would not be correct either. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events