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
When we create issue types in portfolio, if we don't there and then assign a team to the issue, it promptly disappears from portfolio when it is committed. How do we assign a team to an issue outside of portfolio, or get portfolio to display issues without a team assigned
Is there a way that when we create issues in portfolio or indeed outside of portfolio, with a Fixversion that is included in the portfolio, we can get these issues to appear. We keep falling into the trap of Portfolio missing work that has been created.
This is portfolio 3.x the behaviour is different in portfolio 2.x
Answering your question:
"How do we assign a team to an issue outside of Portfolio, or get portfolio to display issues without a team assigned?"
In Jira, you'll need to expose the Portfolio team field, see docs here - https://confluence.atlassian.com/jiraportfolioserver/configuring-custom-fields-935577874.html
In Portfolio, try to add the whole project as the issue source, and not only the board. Alternatively, you can add another filter to the plan's issues sources when the team field is empty.
Let me know if the above makes sense,
Roi Fine | Product Manager