How do I make Assignee a read only field?

[mburke]

I've seen this question asked and answered a bunch but the answer doesn't seem to work for me. For example, in this answer - https://community.atlassian.com/t5/Jira-questions/Make-Assignee-readonly/qaq-p/10960 - it says to remove the Assignee from the screen that is associated with the Edit operation. Well I've done that and it hasn't changed anything. I am still able to edit the Assignee. 

In a related issue, when I was trying to test making a custom field read only I was also unable to do that. I have the custom field added to the 'view' operation, but not included in the 'edit' operation. But the custom field doesn't even show up in the ticket if its not in the 'edit' operation. Am I missing something?

[Jack Brickey]

What about removing Assign issues permission from all but those you wish to allow that privilege?

You can also consider this...

Place the property below on any status where you do not want to allow changing the Assignee.

jira.permission.assign.denied

There is a good article on properties if you are not fluent with properties - http://www.j-tricks.com/tutorials/permissions-based-on-workflow-status

[Rimantas Andrulevičius]

If this is still relevant to someone, there is an official Atlassian doc (workaround) for this kind of case:

https://confluence.atlassian.com/jirakb/how-to-restrict-the-assignment-of-issues-that-are-already-assigned-to-someone-1168846611.html 

Also you can vote on this bug and feature request:

https://jira.atlassian.com/browse/JRACLOUD-77086

https://jira.atlassian.com/browse/JRACLOUD-82044

[Edwin Kyalangalilwa]

Hi @mburke ,

An option would be to use the Assign Issues permission in the permission scheme. So you can make it so, some users or groups can't assign issues.

Permission to assign issues to users. It also allows autocompletion of users in the Assign Issue dropdown. See assignable user permission below for more information.