nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Karie Kelly1

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.

Accepted answers

Jobin Kuruvilla [Adaptavist]

Look at the behaviors plugin:

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

All comments

Jobin Kuruvilla [Adaptavist]

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.

Karie Kelly1

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-cloud