nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Managing Shared Teams in JIRA

James Brown_obrwgo

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?

Comments

James Brown_obrwgo

Any ideas out there?

Roi Fine

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?

Cheers,

The Portfolio for JIRA team

James Brown_obrwgo

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

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

James Brown_obrwgo

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

agile

advanced-roadmaps

team