How do I make a field read-only on edit based on another field's value

[Karie Kelly]

I cannot locate how to make a field as read-only or not visible, when the user Edits a jira item, based on either a specific status or preferable another field's value. Basically, we have to move items to another system at a certain state and don't want users to update various fields if the item has been moved.

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

Look at the behaviors plugin:

https://studio.plugins.atlassian.com/wiki/display/JBHV/JIRA+Behaviours+Plugin#JIRABehavioursPlugin-Makeafieldwritableonlyifacertainvalueissetinanotherfield

[JamieA]

Do look at it, but you won't be able to use it with ondemand.

[JamieA]

I thought you could not use javascript in ondemand... can you?

[Jobin Kuruvilla [Adaptavist]]

OnDemand! You can probably mimick the same using some Javascripts on onDemand though.

[JamieA]

I thought they stripped out javascript, but yeah, that's how you do it in hosted jira. Would be interested to know.

[Jobin Kuruvilla [Adaptavist]]

Shouldn't it be possible to do so in field configurations? I am not sure either!

[Karie Kelly]

Appreciate all the quick feedback; but, yes, we are very limited in OnDemand. I checked field configurations, but I've not seen that you can control whether it is read-only or not, or visible or not. Seems you can only control visibility on a screen. But, there is only one edit screen that is defined for the workflow vs being able to apply conditions when the edit sreen renders.

Any other advice on options is greatly appreciated!

[Karie Kelly]

I ended up making different workflow transitions based on the different field values using conditions that had different screens and removed the field and then I added the property to the state to not allow it to be editable.

For example, I could have 4 different Update transitions - each with a different condition.

Lots of work for not having this capability in OnDemand.