You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Our IT group is organized into 13 functional agile teams. As projects come into the queue, they are divided up into work that can be done by multiple teams based on the services or UIs that need to be updated. We would like to create one set of Epics for the project, then determine which teams have work to help complete each Epic. We are about to implement Portfolio for Jira, and would like to set up each of our functional teams as a shared team so that we can view the project work across those teams. This is working great in our testing at the story level, but we are only able to assign one Shared Team to an Epic, so it does not show up in any of the plans for the other teams.
I'm wondering if we are using Portfolio and the Shared Team concept in the way it was designed. Can you provide any insight?
Kelly - FirstBank
You can only manually assign one team to an issue (may it be an epic or a story) in Portfolio, the intention of manually assigning being: "Don't try to figure it out for me, this is the team that will be working on it".
I understand in your case the interesting part might be more the roll-up of teams used in the epics children, in which case I'd suggest not trying to assign manually a team a let it roll up in your plan. You might also wanna ensure the issue sources include those epics without a team on top of the filtered stories you already have.
Let me know if that helps!