Unable to Restrict Assignable User to Only Members of a group picker Field

[Sandra Arday]

Hi Everyone ,

I'm trying to restrict users from assigning issues if they are'nt part of a single picker field 

I realised when i revoked their roles assignable user permission , users couldnt assign issues at all .

I would like users to assign issues to users in their group based on the group picker field 

Has anyone tried this before , if yes how did you go about it 

I'll like to hear your feedback

[Nacho Moreno Ortega]

Hi @Sandra Arday ,

I am Nacho and i am part of Decadis.

If the desired requirement is that the assignee must belong to the group selected in a Group Picker (single group), this can be easily achieved by using a Jira expression validator from our app Jira Workflow Toolbox Cloud .

The following Jira expression can be used in the validator:

issue?.assignee.groups.includes(issue?.customfield_NNNNN?.name)

"NNNNN" must be replaced with the id of the Group Picker (single group).

This is how the result would look like if the validation is not met:

If you decide to try it out and if you need any kind of assistance with it, please feel free to create a request in our support portal .

Best regards,

Nacho

[Jayesh Raghuvanshi]

@Sandra Arday 

Add a Group Picker custom field (e.g., “Assignment group”) and make it required or set by automation up-front

Add the workflow property to the statuses where you want the restriction enforced: set jira.permission.assignable.groupCF with the field’s ID, so only users in the selected group are assignable in those statuses

If you need to further control who can change the assignee, you can also restrict the “Assign issues” action similarly at those statuses using jira.permission.assign.groupCF

If you prefer a guardrail rather than blocking UI selection, add a rule: Trigger “Issue updated” with “Assignee” changed; JQL condition checks the current issue like: assignee in membersOf('{{issue.customfield_12345.name}}');

Recommened MArketplace apps for your solution

JMWE  

ScriptRunner for Jira Cloud

JSU/JWT (Cloud)

Refernece articles for the plugins 

https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465242916/User+Validator
https://docs.adaptavist.com/sr4js/9.x/features/workflows/validators/user-in-field-s-validator
https://appfire.atlassian.net/wiki/spaces/JSUCLOUD/pages/1973288961/JSU+Rule+Builder+-+Validators
https://community.atlassian.com/forums/Jira-Service-Management/Limit-Assignee-to-member-of-Assignment-Group/qaq-p/1833067

Thanks
Jayesh R

[Marc - Devoteam]

Hi @Sandra Arday 

This could be done by the use of marketplace apps that extend workflow options, like JMSE, JWT, JSU, Scriptrunner, etc...

Ootb this is not possible.

The only ootb work around, you can do is to have an automation in place that based on assigning an issue check the value of the field doesn't contain that user, and then revert the assignment action

[Sandra Arday]

Hi @Jayesh Raghuvanshi @Marc - Devoteam 

I tested it again and it works 

by setting the group user field as an assignable user . Only individuals in a selected group can access thickets

[Jayesh Raghuvanshi]

@Sandra Arday  If you like the suggesstion kindly accept the answer, it will be helpfull for me.

Thanks
Jayesh R