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 to set custom field mandatory based on select list custom field option?

Serj Shcherbakov

Hi!

Can we set a custom field as mandatory based on another custom field value at issue creation stage? (with Simple scripted validator)

I Have:

"customfield_17212" (Select List) with optioins: 23742, 23745, 23749, 23753 - if filled (condition).

"customfield_10355" (Select List) - must be required.

I think this script can help me, but, it is not working.

import com.atlassian.jira.ComponentManager

FormField field1 = getFieldById("customfield_17212")
FormField field2 = getFieldById("customfield_10355")
if(field1.getValue().equals("23742","23745","23749","23753"))
{ field2.setRequired(true) }
else { field2.setRequired(false) }

Please help me,
Sergey.

Accepted answers

JamieA

That code above is for behaviours.

If you are using simple scripted validator, the code might be

(! cfValues["Name of first select"]*.value.intersect(["val1", "val2", "valn"])
 || cfValues["Second select"]

So to translate that, if the selected value in the first field is not one of the ones you care about, then fine, if it is then the other field must have a value.

A SSV is a simpler and more reliable method than using behaviours, the advantage of behaviours is that the second field becomes required as soon as they change the first field.

Note I'm using field names and field values, not field IDs and option IDs. This makes it more portable.

All comments

JamieA

That code above is for behaviours.

If you are using simple scripted validator, the code might be

(! cfValues["Name of first select"]*.value.intersect(["val1", "val2", "valn"])
 || cfValues["Second select"]

So to translate that, if the selected value in the first field is not one of the ones you care about, then fine, if it is then the other field must have a value.

A SSV is a simpler and more reliable method than using behaviours, the advantage of behaviours is that the second field becomes required as soon as they change the first field.

Note I'm using field names and field values, not field IDs and option IDs. This makes it more portable.

Serj Shcherbakov

Hi Jamie,
I'll tried to modify your example like this:

(! cfValues["customfield_17212"]*.value.intersect(["23742", "23745", "23749", "23753"])
 || cfValues["customfield_10355"]

then like this:

(! cfValues["SOW type"]*.value.intersect(["New Solution", "POC/ Prototype development", "SDN/NFV POC", "Upgrade"])
 || cfValues["TOMS Modules"]

But, it still doesn't work for me.

5543.jpg

5543.jpg

JamieA

SOW Type is a multiselect right? It's the second one you should be using. What versions of jira and the plugin are you using?

JamieA

If SOW type is a single select use: cfValues["SOW type"].value (ie remove the asterisk). Also pay attention to case of the field names.

JamieA

Sorry, should be ! cfValues["SOW type"].value in ["New Solution", "POC/ Prototype development", "SDN/NFV POC", "Upgrade"] || cfValues["TOMS Modules"]

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

jira

groovy

workflow

simple-scripted-validator