I have to say I find the resource view by team to be extremely helpful. Unfortunately, maintaining the teams across portfolios is not working and not very intuitive. Documentation that I can find leads me to global permissions, etc. which is not what I'm looking for.
We have several portfolios and teams. As you can see below on some portfolios they indicate that the teams were inherited from the upper-level. I don't know for sure what that means, but I am unable to add team members from this portfolio so I think what that note is trying to indicate is that the team is a shared team and was not created on this portfolio.
When I look at the teams on a different portfolio, I have the ability to add team members, so I assume this is the global team that is shared across portfolios and if I add a team member here it will appear on all my other portfolios. So I added the new team member on this portfolio.
However, when I go back to the first portfolio, the new team member is not showing on that team. Yet the 'NEW MEMBER' option is greyed out because this team was inherited from the upper level.
I searched through all the global settings I could find thinking maybe my 'upper level' team was defined somewhere else but can't find where that might be.
Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...
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