In Portfolio 2.0 at least, it appears that if a user is on multiple teams, their capacity will be used completely on each team. In other words, if the user is on 2 teams, they will get scheduled into two issues simultaneously (one for each team), utilizing 200% of their time. Is this expected operation?
Yes, this is the expected behaviour. You will need to define how many hours the person spends on which team by filling in the weekly hours under the team-specific availability in their details panel. This gives you the most flexibility in planning and allows you to experiment with what-if scenarios.
For more details have a look here: https://confluence.atlassian.com/jiraportfoliocloud/configuring-teams-members-availability-828785286.html
I was hoping that Portfolio would notice when a resource is overallocated. I have a few resources, typically testing, that bounce between projects, so fixing their hours per project doesn't make sense. If Portfolio had a Global Weekly Hours option, as well as the current Team-specific Weekly Hours, it would be able to determine when a resource is overallocated and schedule out accordingly. That would seem to make more sense to me than just letting resources become committed to way more time than they could possibly do, which leaves it to the Portfolio user to notice this has occurred.
Same scenario as Jason and Josh, I agree and share their frustration.
I have a team of 12 people who work on varios projects and multiple sprints within those projects. I'd like to be able to define one or two teams which arse assigned to multiple boards and projects.
I myself manage, design and develop, and find it unnatural to place myself under a different team for every different board I make.
@steven behnk yes but at the end of the day one of the primary purposes of this tool is to assist in scheduling the portfolio of your projects. You may be perfectly happy for a resource to give 100% capacity to both teams where required and priorities at an epic and story level (manged in portfolio) dictate when they are to be allocated to to these & when. At the moment, they are potentially in 2 places at the one time..... it's a global capacity consideration we're referring to here.
To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events