Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Managing Shared Teams in JIRA

Portfolio Team Field

I have multiple teams that could work on a JIRA Project. We would like to restrict which teams can work on an issue in a project by restricting the shared Teams available in the Teams field in JIRA from Portfolio or JIRA.  We attempted to do this by creating shared teams in Portfolio. We then added the desired shared teams to our Plans that contain JIRA Projects. At this point, we assumed that the list of teams would only be the ones in the Portfolio plan. It actually had the opposite effect and displayed all of the shared teams and would not allow us to add teams specifically that would only work on a specific project. My next attempt was to create a custom configuration for the field, but JIRA doesn't let you do this because it comes from Portfolio.

Are there any ideas about how to manage Portfolio Teams?


Any ideas out there?

Roi Fine
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 12, 2017

Hi James,

The Portfolio Team field, when surfaced in JIRA, only populates the shared teams(configured in Portfolio). Currently there is no option to restrict certain teams from certain projects.

Can you shed some more light on what are you tring to do and why?


The Portfolio for JIRA team

Ideally we would like to have the Team field in JIRA function the same as it would in Jira with a drop down list, checkbox, etc. and we could also keep a context for projects assigned to plans/Projects. There appear to only be to paths for managing the Team field provided by Portfolio. 1) create shared teams in portfolio, then add them to a plan. This creates an issue because it would make teams available to projects that shouldnt have those teams, and work being assigned to the wrong team. 2) create a team in a plan. This doesnt make the team available in a JIRA project. Thus, the issue cant be assigned to the team. We would then need to create the team as a shared team, bringing us back to the first issue.

Roi Fine
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 13, 2017

Is this request comes from a need to restrict the input for the team field?

The built in function actually places to much restriction and complixity when creating teams. It would be ideal to create teams at a top level in Portfolio that way they would all be available across our business, and we would be able to select the teams in a portfolio if we wanted to.

Any update on this?


Log in or Sign up to comment