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
Next: Root
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.
I am using Portfolio primarily for it's reporting capabilities (the full-hierarchy CSV export). The portfolio includes multiple Jira Software projects. Portfolio "Teams" are based on Scrum Boards in those individual Jira Software projects. Portfolio is automatically associating items to teams; I want it to stop.
At the Portfolio level we identify teams using the Component/s field. If Portfolio insists on assigning teams for me, can I make it use the Component/s field or the Project field as a basis for that assignment?
Portfolio lets you assign a team/ board or automagically assigns it if you have one team/ board (since there is only one team/ board).
If you are using the component field to assign a team, then create the issue and select the component from the drop down in the newly created issue row. You may need to add the component field using the little tool gear toggle.
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.