How to allow editing only one field in Jira Cloud?

[Naresh Sampath]

I’m using Jira Cloud and want users to edit only one specific field on an issue, while all other fields should remain read-only (not editable).

Is this possible? If yes, can anyone guide me on how to do this?

[Rik de Valk _Brainboss_]

Hi @Naresh Sampath , 

I would solve that by using a Workflow transition with a screen that contains only that field. 

The exact way you would implement it depends on other context. But the high level solution design would look something like this: 

1. Remove the field "Field X" from the Edit screen for that work item type
2. A new Screen with only this one field "Field X" on it
3. A Workflow transition 'From any status, to Itself" (circular), with this new Screen applied to it

The details about permissions on the project, user conditions on the workflow transitions depend on the context of your scenario. 

But maybe this highlevel design helps!

Have a nice day. 

Rik 

[Naresh Sampath]

Hi @Rik de Valk _Brainboss_ 

Thanks for Your reply!

I am already using this approach to edit a single field through a transition screen, as you mentioned above. Is there any other way to solve this problem?

[Staffan Redelius]

Hi @Naresh Sampath 

I can confirm that the solution provided by @Rik de Valk _Brainboss_ is the way to go to resolve this. 

It locks down jira very much. If you want more flexibility you could set a conditon in the workflow that allows users that belong to certain groups to do transitions to other states with the ability to update other fields in specific transition screens.

There might be third-party apps that can resolve it in other ways. Is there a specific reason for you to look for another solution than you already have in place?

Best regards,
/Staffan

[Daryl Marsh]

If you have ScriptRunner for Cloud available, you can use behaviors to make read-only fields to a group of users.

[Rik de Valk _Brainboss_]

Another approach is not to lock it down, but to monitor it and optionally revert the change. 

You could implement an Automation Rule that triggers on the Field Change. 

Whenever this field is changed, you could

• Revert the value back to the previous value (by accessing the {{fieldChange.from}} value)
• Send an email to the user who triggered the event (who changed the value) that this is their first strike. And if they do it 3 times, they are fired 😄

Cheers, Rik

[Aron Gombas _Midori_]

There is no field-level "edit" permission granularity available in Jira. It has been a debate for longer than a debate, but due to the complexity it would create, Atlassian didn't implement the request.

At the same time, there are third party apps that offer this, at there was at least one for Jira Data Center. It is a rather hard problem, so I am not sure if these apps can protect the field from every angle (API calls, automation rules, etc.).

Also, I don't know if those were ported to the Cloud, but do your own research on Atlassian Marketplace if you are open to using third party apps.

I'd start with this app: https://marketplace.atlassian.com/apps/1226365/secure-custom-fields-for-jira-security-permission?hosting=cloud&tab=overview