Configure Teams dropdown so that list of Teams depends on which Jira Project you are in

[Jean Sandberg]

My organization has a few dozen Teams. This means that when a user clicks the Team dropdown on an issue, the list of Teams is quite long. I would like to set it up so that different Jira Projects are tied to a subset of Teams. I would like to set it up so that for Jira Project A, the options for the Team dropdown are Team X, Team Y, and Team Z only. For Jira Project B, I want the options for the Team dropdown to be Team A and Team B only. This not only makes choosing the Team less unwieldy, but it would also prevent an issue in a Project from being set to a Team that has nothing to do with that Project. 

I have searched Community and documentation and I do not believe this is possible. We have been working around this by using custom fields. However, I really want to use the built-in system Team field because Atlassian has recently unified Atlassian Teams with the Teams in Advanced Roadmaps. 

I see that Contexts can be used to achieve this type of functionality but only for Custom Fields, and not System fields.

I'm 99% sure that I am out of luck but wanted to confirm with people who know more than I do.

[Francis Batilo · Accepted solution]

@Jean Sandberg

You are correct. So far there isn't a way to limit the options for the native team field. 

As a workaround, you already alluded to using a custom field to leverage the missing feature. You could also try using Jira automation to automatically assign a team based on certain criteria on the issue, say the assignee or something else.  

Let's hope there would be more updates to the team field in the future!

Cheers,

Francis

[Jean Sandberg]

Thank you for the quick confirmation, Francis! We could probably use automation that looks at the existing custom fields we have for "teams" and uses that to auto-set the Jira system field for Team. As I said, I want to take advantage of Teams in Advances Roadmaps.

Cheers,

Jean

[David Friedrich]

Hi @Jean Sandberg

not sure if this would work 100% satisfactorily, just as an idea maybe worth trying:

Whenever I want to limit something in a list field, I look at behaviors (scriptrunner). Not sure if it is possible to a) use the project as a condition in this case and b) if behaviors work with locked fields at all. But maybe worth a try.

[Jean Sandberg]

Thanks for the idea David!

Best,

Jean