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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Most organizations using JIRA create one project per team. However, I am also aware of some organizations that have multiple teams using one project. They then use labels or components to filter out their Scrum boards.
Does this work well with JIRA Portfolio? Can multiple teams share one JIRA project, then separate teams into different Scrum boards and logical teams in JIRA Portfolio using labels and/or components? If it does work, what are the pitfalls if any?
Seeking the same answer Chris.
I have 12 projects, of this one project in Jira has 4 teams using components to filter 4 boards and sprints for each team.
I need to find a way for Portfolio to report for each board, so I have created 4 teams in portfolio and assigned each a board for their scope. Portfolio doesn't seem to like this as it is not reflecting the correct scope and backlog items are not accurate. Items are missing and the results change depending on how you apply Portfolio out of the box filters.
Did you ever get your answer?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.