How can I make a field editable only for some role?

[Luciana Di Matteo]

Hi, 

I want that the fixed version is only editable for some role 

Can you please help? 

[Nic Brough -Adaptavist- · Accepted solution]

You can do this without add-ons, but it means moving the edit into the workflow.

Take the field off the issue edit screen, as mentioned above.  This allows you to create an issue with it, but then no-one can change it.

Add transitions to the workflow, such that:

• They go back to the current status
• They have "transition screens" screens that include the field
• They have names like "Edit <field>"
• They have "conditions" on them that only allow your one role to use the transition

[PADMA KOTHAKOTA]

It is possible using Behaviors. You can restrict the field for particular project role

[Luciana Di Matteo]

what is Behaviors? Thanks 

[PADMA KOTHAKOTA]

Behaviours is a Jira plugin it defines how fields behave for issues in a given project or issue context.

For more info check the below link

https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html

[Azfar Masut]

https://scriptrunner.adaptavist.com/4.2.0.7/jira/recipes/behaviours/field-readonly-except-role.html to be exact

[Somesh Sahoo]

By automation you can give the edit access to a particular user for other if they edit the value it will be reversed to the original value.
implemented and working fine 

[Liam Maeder]

This is a missed oportunity that has been requested by my own team members on Server a couple of times, nothing short of a plug in helps.

Does anyone know of an open task to vote for? Or how to log these tasks?

Thanks

[Nic Brough -Adaptavist-]

There have been a number of requests in the past, but Atlassian have closed them all with "won't do this".

You could try raising another over at https://support.atlassian.com/contact but I'd expect it to be closed as a duplicate.

[Nir Haimov]

You can't do that in Jira Cloud.

The use of Behaviours that @PADMA KOTHAKOTA suggested is only for Jira Server.

Also, this solution is for Server using a 3rd part add-on named ScripRunner, it's not a build in feature in Jira either in Cloud or Server.

[Luciana Di Matteo]

Thanks @Nir Haimov, so no way I can not allow a field to be edited by anyone? 

[Nir Haimov]

Id you don't want the field to be editable at all, then remove it from the "edit" screen.

If you want the ability that some people will be able to edit the field and some not, well, you can't have this.