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 Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Thursday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

94 views 0 5
Read article

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