Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
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 Portfolio Capacity calculation

A question for Jira Portfolio use:

How does Portfolio calculates team capacity for future capacity? Our team sprint capacity is 348  hours per sprint (2 week). Portfolio looks like this for future sprints. Why isn't the sprint (2) full instead it calculates work  also for sprints 3 to 6? We don't have any dependencies in our stories. Shouldn't almost all capacity be on the sprint 2?2018-05-29_12-03-05.jpg 

1 answer

0 votes
Deleted user May 29, 2018

Hi @Teija Kurttila,

The scheduling behaviour takes into account multiple data points within JIRA. This could be why sprint capacity could be left over.

See a similar question with a response from an Atlassian Team member. 

Hope this helps

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events