We are currently evaluating the portfolio and have come across an issue where we assign a member to more than one team (they may have a required skill) and the effective member 'resource' count doubles automatically.
If say 2 epics are scheduled for the same release with the 2 separate teams, it will appear as if that member has double hours available per week without changing the availability in team (manual override) and the schedule is not accurate.
We know you can override it manually, but when scheduling across a larger number of projects and different 'multi-membership' people it becomes too error prone. To work around the problem we currently just use one team and assign to epics individually (not ideal). The schedule will always assign the user to the highest priority epic and won't overstate their resource count, etc.
So ideally when a member is in multiple teams it would work the same way and avoid the need to micro-manage the availability in a team to solve.
Is this a known problem or is some setting available to prevent the double up issue?
Hi Barnaby, this is a known topic but has been a conscious design decision in a first step given the number of different usecases and variations we've seen related to this, thus we've started out with giving manual control over the availability in a team. There is an open suggestion ticket related to this: https://jira.atlassian.com/browse/JPO-114 - please make sure to vote for it and comment on it if it does not cover everything.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG