I have a portfolio plan spanning across two projects, each representing firmware development for a different product.
We only have one shared firmware team who are working on both projects, but portfolio requires that teams are associated with only a single project or board and without this sprints created in portfolio can't be automatically generated in their respective projects.
How do we resolve this?
I have considered creating a team for each project with identical members and halving their velocity but this would presumably mess-up auto-planning.
Unfortunately in Portfolio you can only associate one team with one board. If you want to use a shared team, what you will have to create 2 separate plans for your projects and then when you add a new team to your second project, you'll be able to select the shared team. If you just put a user from another team to use that issue, Portfolio will schedule the issue into the team that this member is in and the board associated to it.
If the upper solution doesn't work for you, you could try and set the issue source to be a filter, which would include both projects and see if that will work for you.
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