Editable List Used by Two Pick Fields

[john]

I am working on a cross-team workflow (more "process management" than "software"). Basically, if Team A needs to ask Team B to do work, we want to submit that request and allow Team B to manage the request based on their capacity. In this particular case, we also want the definition of team to be flexible and manageable within the project. Essentially, we want to be able to manage the list of teams like we can manage Components in a software project. Then, we would have two pick lists on the same issue: "requesting team" and "assigned team." Both of those pick lists would be able to pull from the same list of team values.

I don't see any straight-forward way to do that in Jira and was hoping for some suggestions. Thanks.

[Antoine Berry]

Hi @john ,

Why not using group picker fields ?

[john]

The "teams" I want to identify are fluid. They don't align with business unit structure that is mirrored in our permissions structures. Teams can form and go away rapidly. Updating users and groups takes significantly more time since it's an internal service desk request. 

[Antoine Berry]

Well you can achieve that by using select lists for both these teams. This is easy editable and you will not have to manage groups.

The downside is you cannot grant permissions according to that "group". And you need to train your agents to use filters that are based on this value.

Antoine