Capacity in Portfolio 3+, does individual availability (in a shared Team) affect the team capacity?
Asked by Cathy Rivard:

[This article](https://confluence.atlassian.com/jiraportfolioserver/changes-in-the-new-experience-961780550.html?_ga=2.242812998.53283767.1562763711-142540950.1542301518) refers to changes in managing capacity in the new planning experience.

In particular this section:

"In the improved interface, we're still considering how capacity is best managed. We're starting with the following details:

* Individual capacity planning is replaced by ***team capacity planning***.
* When optimizing a plan, Portfolio for Jira will consider the ***total capacity of a team*** to complete the work being scheduled.
* For Portfolio for Jira to do this, you must directly set [team capacity](https://confluence.atlassian.com/jiraportfolioserver/managing-teams-952623602.html) in your plan."

It's still possible to set hours/availability for individuals in a Shared Team. I understand that things like dates aren't considered any longer, but what about the team capacity when members are assigned? Will it reflect the individual team member availability? Or do I need to manually adjust the team capacity in the plan?


Answers:
author: Earl McCutcheon
body: Hi Cathy

There is not currently an an option to set hours/availability for individuals users.

First point I would like to address is that Capacity in the 3.0+ new experience is currently visible on a per-team basis as you noted and covered on the changes in the new experience article you linked. However this is an area we are targeting for improvement in the future to include individual capacity back in from all the user feed back we have received on the feature, and we are tracking this at the following link, make sure to add a vote or any comments on ideas you have to make the feature better as covered in the [implementation of New Features Policy](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html):

* <https://jira.atlassian.com/browse/JPOSERVER-2562>

Touching more on the differences between the live plan and the new planning experience, in live plans Portfolio used the concept of "team members" which were independent from "assignees" in Jira. So previously you had to assign an issue to a "team member" in Portfolio and, when you saved this change to Jira, the issue was then assigned to the corresponding "assignee" in Jira and the items were separate entities and mapped to each other.

In the new planning experience In Portfolio 3.0 and later, we've removed the mapping of assignee to the team member and you set the "assignee" field directly in your plan. This effectively removes a few extra steps and some application overhead so you now can assign an issue to only one assignee where previously the team was a pool of users, however as there is not currently individual capacity regardless of the assignee set on the issue the teams capacity is what is leveraged for the calculation in the current iteration.

Overall this is a feature that is coming, but we do not have any ETA on the arrival. We are still looking at ways to implement this feature for the new experience leveraging the new way the assignee is handled over mapping a team member, so please add yourself as a watcher on the feature request listed above to get updates, and if individual capacity with availability tracking is a requirement for you I would recomend switching back to the live plan view until the feature is avaliable in the new experience.

Regards,  
Earl

comments: author: Alexander Bondarev
body: Thank you, [@Earl McCutcheon](/t5/user/viewprofilepage/user-id/502460) !

Nice news!


Tags: advanced-roadmaps