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'd like to make a board that shows issues assigned to members of a specific Portfolio team, the reason being that they sometimes work on bugs etc., that don't have the Team field filled out.
If I had used groups instead, I would be able to do like this:
assignee in membersOf("My Team")
but this doesn't work for Portfolio teams. Is there another way?
There might be an option but I think you're not gonna like it. It all goes down to filling out the freaking Team field anyway :)
But automatically. Add a project automation rule to fill out the field with a set value in case a bug is assigned to a certain engineer.
This will essentially gives you two lists (one inside the portfolio team and another inside the automation rule) with a need to keep them coherent but... I have warned you :)
I'd say that the another way would be to find out why the Team field is not filled out for bugs.
Since in the end of the day you want the items to appear on the board then it's the simplest and most probably the most correct way.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It also needs to work for other kinds of issues. For instance, we have a type for questions/decisions. These are normally assigned to people who might know or people with authority and not to a team as such. The team as a whole cannot resolve it. So the team field is normally not filled out on this type.
But automatically filling it out anyway seems like a way that might work. The question question then is whether I can do this easily - I'm only a space admin, not a global admin. I'll find out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.