Restrict the assignable users to a specific user group

Matt February 26, 2015

I would like to Restrict the assignable users to a specific user group Both withing a workflow transition and when viewing a issue.

We are running JIRA v 6.3.9

Any suggestions?

Many thanks

2 answers

0 votes
kitkat
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 26, 2015

You can change the contents of the group based on status, if you have certain plugins in the Workflow's Post Function (there are many that do this) that evaluate a custom field depending on what your criteria is. Once the Post Function changes the group/user custom field's value on the status transition, you can then setup the Assignable User Permission to read off a Group/User Custom Field Value instead. This would make the permission fungible based on how you setup the field's manipulation in the Workflow Post Function (and thus, the status).

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 26, 2015

The list of assignees is determined by the permission scheme.  Look in there for "assignable user", the rule on that line is likely to be something like "Role: Developer".  Either change your project membership (so that your specific user group is in that role and no-one else is), or come up with another rule for it.

Matt February 26, 2015

Hi Nic, Many thanks for your reply, can I set this value depending on status of the issue? ie if the JIRA issue as a status of 'client UAT' then only users with a role of client UAT can be assigned?

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 26, 2015

No, the assignee list is permission based, not status.

Suggest an answer

Log in or Sign up to answer