Differ assignable users for issue vs. sub-tasks

[Mark Wheeler]

I have restricted a Project's Issues to not be assignable to a particular group of users (by not including that group in the "Assignable User" permission at Project level).  However, I want sub-tasks of those Issues to be assignable to this same group of users (that shouldn't be assigned the parent Issue).

I've looked at workflow properties but couldn't get this to work as I think Proporties only affects Transitions, so issues could be assigned using the normal "Assign" button outside of a Transition.

Any ideas how to implement the functionality I'm looking for?  I have ScriptRunner if that helps but don't think it will in this case unless I can get a ScriptRunner script to be triggered by the standard Assign button.

[Petter Gonçalves · Accepted solution]

Hello @Mark Wheeler

Thank you for reaching out.

Per your description, I understand you want to restrict some groups of users from being assigned to issues, however, this same restriction should not be applied to the related sub-tasks. Is that correct?

Actually, workflow properties can be applied to both transitions and status, so you can use properties to restrict which groups can be assigned to your parent issues while your sub-tasks can be assigned by anyone. These would be the exact steps:

1 - Use distinct workflows for your parent and sub-task issues, so the properties will be applied only for your parent issue types

2 - Configure the following property in the statuses and transitions of the workflow related to your parent issues, adding as the property value the name of the groups that can be assigned to the issues:

jira.permission.assignable.group

To add properties to both statuses and transitions:

1 - Navigate to your board > board settings > Workflows > click to edit workflow

2 - On diagram mode, click in the status/transition > Properties:

Let us know if it works for you.

[Mark Wheeler]

Wow wow wow ... you have really made by day!  A thousand thank yous!

My team were going mad as not having this was causing a real headache.

I fell over a little on properties because I didn't realise you could apply them to statuses (sorry relative newbie) and also because on assignment the property restriction allows you to select someone from a non permitted group but on pressing Assign then it tells you that you can't assign to them,  whereas the Permission scheme setting stop the user from even being chosen in the Assignee user box.

Anyway - just tested and will be rolling this out today.

You've made me and many others in my organisation very happy!  Thank you again (if you have an office hero award then you must be nominated for it).

Cheers

Mark

[Petter Gonçalves]

I'm glad to know my instructions have helped you, @Mark Wheeler

Let us know in case you need help with anything else and have a nice day! :)