nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I restrict changes on the Assignee field to Project Admins?

Trudy Claspill

Using JIRA 7.3.6 and Adaptavist ScriptRunner v5.1.6.

I want to prevent the Assignee field from being changed except by Project Administrators.

I found this article in the Adaptavist site about making a field read-only, and applied that to the Assignee field.

https://scriptrunner.adaptavist.com/latest/jira/recipes/behaviours/field-readonly-except-role.html

I then tried to change the Assignee on the applicable issue while logged in as a user that is not an Administrator for the project.

When I clicked on the Assign button in the Issue Details view, the Assignee field was indeed disabled.

However, I was able to click on the Assign To Me link, and the Assignee on the issue changed.

Why doesn't the Behaviour affect the Assign To Me functionality?

Is there another way to accomplish this?

Accepted answers

Nic Brough -Adaptavist-

The behaviour script is not aware of all the different ways Jira might be doing things. The assignee is a field, but the assign-to-me is a separate UI element. You'll need to create another one to get rid of it.

But, you might not need to. You could skip Behaviours entirely, and just use the permission scheme. If you set that up with "assign issues: Role: Admins" (assuming you are identifying the project admins with that role), then that will make the field unchangeable and hide assign-to-me for you.

Tuncay Senturk _Snapbytes_

Hello Trudy,

Another solution (without using Script Runner) is to modify workflow for those issue types.

Remove Assignee field from Edit Screen (No one will change assignee anymore)
Add a transition for every status to itself again (e.g. Open to Open)
Add transition screen which includes Assignee field for this transition
Add a workflow condition to restrict this transition to only Project Administrators

I know, this is tricky and adds a useless transition to the issue history, but it will help you achieve preventing assignee changes from every channel (UI, REST, ..)

All comments

Nic Brough -Adaptavist-

Trudy Claspill

Thank you for the suggestion, Nic, but I can't do this through the Permission scheme.

I want to apply this restriction to a subset of issue types in the project. The permission scheme applies to all issue types.

I will look again at the Adaptavist documentation for information on getting rid of a UI element.

Tuncay Senturk _Snapbytes_

Hello Trudy,

Another solution (without using Script Runner) is to modify workflow for those issue types.

Remove Assignee field from Edit Screen (No one will change assignee anymore)
Add a transition for every status to itself again (e.g. Open to Open)
Add transition screen which includes Assignee field for this transition
Add a workflow condition to restrict this transition to only Project Administrators

I know, this is tricky and adds a useless transition to the issue history, but it will help you achieve preventing assignee changes from every channel (UI, REST, ..)

Trudy Claspill

Hello Tuncay,

Thank you for that suggestion. We have actually already implemented that.

The workflow modification does not prevent use of the Assign button nor the Assign To Me feature. Those are the two features I am trying to block for all but Project Administrators, for a subset of issues types in just one project.

Nic Brough -Adaptavist-

Ok, that's a pain, but it is not going to stop you.

To do this, you will need (at least) two workflows. One for "anyone can assign" and another for "only admins".

In the permission scheme, grant both sets of people the assign rights.

In the workflow for "only admins", use a workflow property (you'll want to add this to all status) to say "only admins have permission to assign issues)

Trudy Claspill

Thank you for that suggestion, Nic.

We already have a unique workflow for these issues we're trying to restrict, so that won't be so hard to implement.

I wasn't aware of the workflow property option for this.

Do you happen to have a link to any documentation that lists the workflow properties that are available?

(Nevermind, I found it.)

Tuncay Senturk _Snapbytes_

Yes, you're right.

Actually one of our clients wanted such a feature and we implemented it for them with a custom plugin.

If you have ability to write your own plugin, I can share the code for you.

Trudy Claspill

I found the way to block the Assign To Me and Assign button features.

Besides using the workflow transitions mentioned by Tuncay, I also used Properties in each status:

Property: jira.permission.assign.projectrole

Value: 10002

This limits the access to the Assign button and Assign To Me features in each status to the Project Role with ID 10002 (which is the Administrator role in our project).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server