Need to set custom fields to Read-only at certain state transitions - having Issue setting Property

Nannette Mori
Contributor
June 17, 2020

At the Done state I don't want any fields to be editable.  I also have certain fields I need read-only at creation and then I have a couple of Fields that I need read-only after transitioning to a certain state.  I know I can create new screens to use at the different work flow transitions but I do not know what to use for the property value for those new screens.  For example on my edit screen is called M2C2 Screen: Capability - Edit.  What would the key be for that screen?  Also Since I need all fields none Editable at Done, and some Fields not editable at creation, and a couple of other fields read-only after a certain state transition do I need to create a screen for each scenario?

We are on Jira 8.6.1 - data center not cloud

1 answer

0 votes
Mathis Hellensberg
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 17, 2020

Hi @Nannette Mori 

Properties is pretty much all or nothing jira.issue.editable = true or false at a certain status.

If you need certain field to be read only after creation you can remove that field from your edit screen and only have it on your view and create screen. 

If you need a field to change behaviour, depending on what status the issue is in I am pretty sure you can do this using Scriptrunner behaviours.

Hope this clears things up! :)

Hari Shankar September 16, 2021

Hi @Mathis Hellensberg 

Is there any possibility from properties  to restrict the editing/updating the custom field value while creation of ticket ?

Mathis Hellensberg
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 16, 2021

Hi @Hari Shankar 

Not to my knowledge, no. But you should be able to with Behaviours using Scriptrunner.

Nannette Mori
Contributor
September 20, 2021

In the documentation in Jira Tips and tricks it states you can lock permissions to a group or role 

 

See Below

 

jira.permission.edit.group = <some Group>

Is the documentation wrong

Suggest an answer

Log in or Sign up to answer