Teams field is single select

Freyr Gudmundson

It's great to have the core Teams field available in JPD. But that field is a single select, and I find myself often having to connect an item in JPD to multiple teams. I know I can do this by using a custom field I create and manage myself, but I would love to be able to do this using the direct connection to the actual Team object in Atlassian.

Can anyone think of a way to accomplish this? I can think of a couple directions, but they all probably require something to be built:

• Make the Teams field multiselect
• Connect each option of a custom field to a Team, maybe in the definition of the field with a simple link.
• Break the item down into several separate items (I'd like to avoid this as it doesn't make conceptual sense at the level I am looking at)
• Rollup field from single select teams field in sub items.

Priyanka Khare

Hello @Freyr Gudmundson 

Currently, the core Teams field in Jira Product Discovery is single-select, which limits the ability to associate multiple teams with an item. Here are some possible approaches:

1. Support multi-select for Teams: This would be the ideal solution, but it requires Atlassian to enhance the native field.
2. Use a custom multi-select field: Create and manage a custom field with team names. While not directly linked to Atlassian Teams, it offers the flexibility to tag multiple teams.
3. Roll up from sub-items: Assign different teams to sub-items and use roll-up fields on the parent item. This works but may not align with your conceptual model.
4. Link custom field options to Teams manually or via automation: Adds complexity and requires maintenance but can simulate a connection to actual Teams.

For now, the custom multi-select field is the most practical workaround until native support improves.