Limit a user picker field (multiple or single) based on a group picker field

[Dirk Ronsmans]

For some time now we have been able to filter a user picker field based on a project role or group(s).

However these are statically defined.

What we have as a use case is that we normally "assign" a ticket to a group and then that group has to choose from their own team who will handle the ticket.

As this isn't possible with the assignee field we add a new group picker field and most likely a new user picker field (which will sorta replace the assignee).

Now the issue here is that we can throw the ticket towards a team but then the assignee field or the "new custom assignee field" can still select from all the groups/project roles that we filter it on. 

Is there any known way to limit a user picker field based on a different group picked field?

This would be nice for both Cloud and Server. (and imho for all types of projects)

[Thomas Opiolka - codefortynine]

Hi @Dirk Ronsmans

you could look at the cloud app External Data for Jira Fields which allows you to create a data source from your local Jira instance by using the REST API.

You can build a search field from groups which is filtered by a dependant issue value. I'm not quite sure if what you're trying to achieve will work, but I think it's worth a try.

For a better understanding, please also visit the documentation.

Thomas

Disclaimer: I am involved in said app.

[Dirk Ronsmans]

Hi @Thomas Opiolka - codefortynine ,

look promising but my fear that this isn't possible out of the box is more than correct then.

Seems pretty sad that such a thing neesd to be handled by yet another addon that does more than we need it to do.

If the need becomes that great I'll take another look.

[Hernan Halabi - Elite IT Consulting Group]

Hello @Dirk Ronsmans maybe you can achieve this using elements app.

https://marketplace.atlassian.com/apps/23337/elements-connect-formerly-nfeed?hosting=cloud&tab=overview

If the group and users would be in an external database I'm certain it would be feasible. Maybe you can solve it directly using the Jira groups. 

[Dirk Ronsmans]

Hi @Hernan Halabi - Elite IT Consulting Group ,

Thank you for your reply.

This might indeed be a good fit if the data was external but that would then require some more user management outside of JIRA. (I could see this perhaps using AD or some other Access Management system tho.

For now tho we would like to keep this inside of JIRA and use the regular groups.

[Hernan Halabi - Elite IT Consulting Group]

Give it a shot if you haven't already. I know it works with internal custom fields just haven't used it for that scenario in the past so I'm not sure if it's going to be a real solution or not

[Julie d_Antin _Elements_]

@Dirk Ronsmans  With the Server version of Elements Connect, you can fetch data from your Jira database (not just external data).

You can check out a bunch of examples of configurations here, as well as download the field configurations to test them out more easily: https://doc.elements-apps.com/elements-connect/latest/?contentKey=examples

There's also a customer story that's similar (but not identical) to your use case that might be useful: https://elements-apps.com/about/clients/cnrs/

The Cloud version is in beta for the moment, so not all of the functionalities on the Server version are available yet.