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

Require Component/s field based on a value selected from a custom field

John Diaz_36y3uf

I need helping creating a validator script (I think) to make the Component/s field required based what the user selects from a single select custom field.

Use Case:

1. Single select drop-down field called "Atlassian Platform" with two value options: Confluence, Jira.

2. If user selects "Jira" from the "Atlassian Platform" field then the Component/s field is required (nothing happens if user selects "Confluence")

Accepted answers

All comments

Ravi Sagar _Sparxsys_

Hi @John Diaz

Using ScriptRunner Behaviours will let you do that easily. Take a look at this script.

Ravi

John Diaz_36y3uf

@Ravi Sagar _Sparxsys_ I appreciate the quick response. Unfortunately, Behavior isn't going to work for me.

There's a certain part of the workflow where I want someone on my team to be forced to enter a Component when moving the ticket "In Progress" ONLY IF "Jira" is selected from the "Atlassian Platform" field. So Component isn't required at the start of the ticket creation and will not be required if "Confluence" is selected.

Apologies for not providing enough context with what I'm trying to accomplish.

PD Sheehan

It is possible to achieve this with either a Behaviour or a validator.

Behaviour scripts are capable of knowing which part of the workflow you are in. This is a good choice if you want to prevent users from clearing the component using the edit screen after it's deemed required.

Of course, a validator will work inherently within the workflow but will allow users to edit the component after the transition has taken place.

A Simple Scripted validator would look like this:

cf["Atlassian Platform"].value != 'Jira' || issue.components

Simple Scripted validators must return a true value to pass or false to generate an error.

A behaviour script would be a little more complicated:

if(!underlyingIssue) return //don't run the validator on create screen when the underlyingissue does not yet exist

def transitionToMakeCompoenntRequired = 'name of transition'
def statusesAfterThatTransition = ['status1', 'status2']
def componentsField = getFieldById('components')
def platformField = getFieldByName('Atlassian Platform')

def isTargetAction = actionName == transitionToMakeCompoenntRequired 
def isTargetStatus = underlyingIssue.status.name in statusesAfterThatTransition
def isRequiredValue = platformField.value == 'Jira'

def componentRequired = (isTargetAction || isTargetStatus) && isRequiredValue
componentField.setRequired(componentRequired)

John Diaz_36y3uf

@PD Sheehan Unfortunately the simple scripted validator didn't work. I also ended up having to change my custom field name from Atlassian Platform to AM Application.

PD Sheehan

Sorry... I was sloppy. It should be "cfValues", the built-in variable that scriptrunner offers that includes all the custom field values in an easily accessible map.

cfValues["AM Application"].value != "JIRA" || issue.coponents

John Diaz_36y3uf

Bummer, still not working. I tried with both single quotes and double quotes.

cfValues['AM Application'].value != 'JIRA' || issue.coponents

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

adaptavist

validator