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

Advanced Roadmap - Kanban Capacity Distribution

Usecase: We are trying to plan capacity across several epics using Kanban. The assumption is that capacity would be distributed evenly across multiple weeks, but for a larger user story it seems to have assigned the bulk of the estimated hours to the end of the date range. 

Does anyone know if there is a setting I'm missing. We'd like to see if our planned work is putting a team over/ under capacity.


Screen Shot 2022-02-02 at 9.57.32 AM.png

1 answer

I have been using Roadmap for a year. capacity was distributed evenly across multiple weeks. 

Something changed this year (beginning of 2022) and it works differently now. 

At first glance it seems like it fills up weeks to the left first, but without exceeding the available resources for the week. It then puts all excess work to the last week. 

This does not highlight overbooking as well as before. All overbooking happens in one week now, instead of clearly seeing "areas of overlap".

If that is the only difference, I think we can get used to it. What I see on your screenshot is that the capacity is put on the last week without having used up weeks prior. That of course would be completely unacceptable. 

The documentation still describes the old behavior

Thanks for sharing the link. It looks like it is supposed to equally distribute among the weeks - which is what I would expect.

Is there no fix for this yet? It renders the capacity view useless for Kanban if the last week is overloaded and the previous weeks are underloaded.

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events