Why is a custom field editable when issue is in a state with jira.issue.editable set to false?

If have set the property jira.issue.editable on a status FROZEN to the value false.

The edit button disappears and standard fields are locked from inline-editing, but custom fields remain editable.

Any chances to lock them down as well?

thx in advance

1 answer

Did you publish the workflow with this workflow property? Is the project using this workflow? Can you double check what status did you put the property?

Yes, doublechecked everything, published, assigned ... everythings fine.

I just noticed that the behaviour is correct after a reload.
Directly after pushing the "freeze" transition button, the Edit button is gone, but the custom fields are editable. 

But saving results in an error message. So it is just a minor rendering issue.

So this is actually working now? It might be a browser cache issue then?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,844 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot