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; } } }

Show/hide custom field using Behaviors from Adaptivist

Jeanne Howe

We are trying to view/hide a text field based on the value of the JIRA Flagged field. We have the following script set up:

def reasonForBlock = getFieldById("customfield_16560")
def flaggedField = getFieldById(getFieldChanged())

def selectedOption = flaggedField.getValue() as String
def isImpedimentSelected = selectedOption == "Impediment"

reasonForBlock.setHidden(! isImpedimentSelected)

We have applied this to the Flagged field (a checkbox field)

Expected results - the text field would remain hidden until the Flagged field was set

Actual results - the text field is not visable when the Flagged field is set

Accepted answers

Jonny Carter_3nm6du

So, I was able to hide a field using this behaviour just fine. A few thoughts:

Be aware that behaviours only function on the create/edit screen, and to a lesser extent things like workflow screens and similar views. Hiding fields from the View Issue page isn't really what they do. There is technically a beta feature to do that, but it requires converting fields to a particular type, which can be a bit dodgy.
Are you doing this in an initializer? It should be a behaviour script on the Flagged field itself.

All comments

Jonny Carter_3nm6du

So, I was able to hide a field using this behaviour just fine. A few thoughts:

Be aware that behaviours only function on the create/edit screen, and to a lesser extent things like workflow screens and similar views. Hiding fields from the View Issue page isn't really what they do. There is technically a beta feature to do that, but it requires converting fields to a particular type, which can be a bit dodgy.
Are you doing this in an initializer? It should be a behaviour script on the Flagged field itself.

Jeanne Howe

Hi Jonny,

Thank you for the response.

I am not trying to hide the field on the view screen (if it's empty it will not display) I am looking at the create and edit screens.

I have the text field hidden initially, but my expectation was that, on the edit screen, once I checked the Flagged field, the text field would then be displayed. This is where I am having issues.

If I could figure out how to add an attachment, I could show you what I am seeing

Jeanne Howe

Aidan Derossett [Adaptavist]

As Jonny mentioned before, you won't see the behavior that you are expecting if you have set up an initializer. An initializer should only run when the screen is first loaded and, therefore, a change to the form field won't be caught after its initial execution.

So instead, you should set up a behavior that is mapped directly to the Flagged field. I'll attach a couple of screenshots to help. Screen Shot 2017-06-19 at 11.09.24 AM.png

Sema YILDIRIM_l6o5in

Hi there is more than one "add context" in "select single". How do I make the corresponding "select list" according to my "numbers" I want?

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

adaptavist

addon-com.onresolve.jira.groovy.groovyrunner

behaviours