How to freeze / lock an issue from editing in a certain status

[Jon]

Is it possible to lock an issue from being edited if its in a certain status or a certain field is filled in? Or have any suggestions on add ons that could do this in the most simple way? 

[Alexey Matveev]

Hello,

You should use workflow properties. You can find more info here:

https://confluence.atlassian.com/jirakb/how-to-limit-editing-permission-to-certain-groups-for-a-particular-issue-status-802171723.html

[Jon]

hi Alexey, is there a way to do this based on a field being filled in instead of based on the status? for example, if XXX field is filled in then YYY Field is locked. in user needs to change YYY field they have to delete XXX field.

instead of groups could we do something like it is limited to be edited by the user that entered them? 

[Alexey Matveev]

Hello,

It is not possible on cloud.

[Tom Lister]

Hi @Jon

As well as the status properties you can use Scriptrunner plugin Behaviours to control fields on screen based on scripted conditions

[Jon]

How would you implement this? In the work flow? I have scriptrunner or is it a different type of scriptrunner 

[Tom Lister]

Hi

If you are familiar with Adapavist Scriptrunner Behaviours

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

then the code to set a field ready based on another field would be something like

log.warn("setting conditionField");
def EARequiredfield = getFieldById("customfield_10300");
def EARequirements = getFieldById("customfield_10301");

 

def EARequired = EARequiredfield.getValue();
log.warn("10300 " + EARequired)
if (EARequired == "Yes"){
EARequiredfield.setHelpText("test: " + EARequired );
}
else {
EARequiredfield.setHelpText("test 1: " + EARequired );
}
//EARequired.each { selectVal ->
if (EARequired == "Yes"){
EARequirements.setReadOnly(true);

log.warn("source value: " + EARequirements.isHidden());
}
else {
EARequirements.setReadOnly(false);
 log.warn("source value: " + EARequirements.isHidden());

//}
}

[Jon]

Hi Tom, thanks for the suggestion, unfortunately I have Jira Cloud, and as I understand it Behaviors are only available for server.