Make certain fields editable in certain status only

[Dominic Asche]

Hi JIRA community,

I want to realize the following szenario within jira cloud:

• issue transitions from status A to B (via automation or workflow transition)
• description and customfield 123 are no more editable for any users
• once issue transitions back to A, fields are editable again

I've tried a lot of things before, but none worked out, like:

• Via my workflow > Transition Properties > jira.permission.edit.description set to false or denied
• Via automation > Set entity property > jira.permission.edit.description setted to false or denied

I'm aware that Permission schemes can allow or disallow the edit of an issue, but I need it:

• for certain fields
• in certain status

Thanks a lot for any ideas

P.S.:
I tried https://community.atlassian.com/t5/Jira-questions/I-want-to-restrict-to-edit-the-quot-Summary-quot-and-quot/qaq-p/920970 but I think it is from 2018 and no longer a solution

[Dave Mathijs]

Hi @Dominic Asche welcome to the Atlassian Community!

To my knowledge, you cannot make a specific custom field editable in Jira Cloud.

See documentation article Use workflow properties

It doesn't mention the use of a custom field id as possible key.

Not entirely sure though, so if other community members could either confirm or object, that would be nice.

[Dominic Asche]

Thank you for your quick response. I’ve tried several times, making multiple attempts and iterations, but I haven’t been able to apply an edit permission to a specific field. Based on my experience, I can confirm that the documentation is accurate, and setting a custom field edit permission is not possible.

As a workaround, I’m now using jira.permission.edit.projectrole as a Property Key for specific statuses to prevent certain users from making edits in those statuses.

[Hans Polder _Devoteam_]

@Dominic Asche ,

As far as I'm aware, it's not natively possible in Jira to restrict only specific fields. You could look at third party apps (which are often paid, by the way) like Scriptrunner to configure Listeners and do the same.

Alternatively, you could still solve this using the Workflow Properties (blocking everything) and using a Self-Transition (so, a transition from Status A to itself (Status A), adding a screen to that transition, and adding the fields that are allowed to be edited.

Some documentation on how this works in DC: How to only allow certain fields to be editable depending on Status | Jira | Atlassian Documentation. This ide translates pretty well to how it works in Cloud too. For documentation on how to do it correctly in Cloud (blocking all edit actions in a certain status, check out: How to restrict editing of an issue in a specific status | Jira | Atlassian Documentation).

Best of luck! If you have any questions, feel free to reach out.

[Dominic Asche]

Thanks Hans for your quick reply and help