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

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
4,508,864
Community Members
 
Community Events
181
Community Groups

How does FREE CAPACITY calculation works in Portfolio Plan capacity view?

Edited

Why FREE CAPACITY is still left? I mean why work is not planned for all week fully?

 

The conditions are as follows:

1 team works 120h per week. Team has 2 tasks: 120h and 40h. There are no memebers included in team, weekly capacity is assigned on team level.

Portfolio capacity divides work in 2 weeks, but neither CW30 or CW31week is fully filled. Why? Especially why there is still 8h left as free in week CW30?

Capacity view

 Taks view

Is there any explanation? Because in documentation it is said that "free capacity is amount of free capacity after usage", but why all CW31 time is not used?

2 answers

0 votes

Hi @Salomeja,

There are quite a few reasons that there is capacity could be left over. The main thing to understand is that the scheduling algorithm believes there is nothing that it is able to schedule. 

As an example of what could be at play:

  • there is no issue estimated small enough to still fit in the sprint
  • there is work available, but nobody with the right skills
  • there dependencies set up that push issues back
  • there are earliest start dates applied that push issue back

Have a look at the following page if you wish to learn more about how the scheduler works. 

https://confluence.atlassian.com/jiraportfoliocloud/scheduling-behavior-828785428.html

Cheers,
Allard

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events