You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Example, if my full teams capacity is 30 points. Say 2 team members are on vacation during the sprint. i would want the velocity to be 25 points that sprint.
Would also be great to control hours available per resource by sprint.
Portfolio tries to schedule work as early as possible without violating the capacity limit of the resources. The Scheduling algorithm assigns work, taking into account team members' weekly availability and the amount of work to be completed.
Let me know if this helps!
Thank you for the reply. I did see how to change team member's availably by hours or points. That provides a low to medium planning accuracy and it assumes the same value to all future sprints.
What would be great is to allow a team to manage the availability by sprint and plan into the future. Manage capacity by point or hours at the iteration level. This would allow JIRA Portfolio to align with Safe PI Planning.
We currently do this out side of JIRA Portfolio and planning predictability is much higher then the Scheduling algorithms. Would be a great future enhancement to Portfolio. If the application is capacity aware, then it also opens up many other metrics and benefits to the team.
Please let me know if you need any additional information.
Hello I am having the same issue. We have Advanced portfolio on Jira cloud & tried changing the Future capacity from the timeline as Atlassian suggested in documentation but it can’t be edited.
i also put in the vacation for my resource in September but it still allows tasks to be assigned to him in September with no Specific warning Or block.
please can we have an urgent solution? All future sprints are not the same capacity and it needs to be editable either manually (points) or via vacation relative points availability.