How to set custom field mandatory based on select list custom field option?


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")
{ field2.setRequired(true) }
else { field2.setRequired(false) }

Please help me,

2 answers

1 accepted

2 votes

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.


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.


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?

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.

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

Jamie, many thanks you, but we still need your recomendations. 1. SOW type and TOMS Modules is Select List (multiple choices) 2. A new scrip ignore SOW type values and always alert the TOMS Modules is Required. 3. We use Jira v. 6.2.3 and Script Tunner v.2.1.17 I hope we solve this issue. Thanks for your co.

Alright I have actually tested this: if (cfValues["MultiSelectA"] && cfValues["MultiSelectA"]*.value.intersect(["AAA", "BBB"])) { if (! cfValues["Subcomponent"]) { return false } } true

note - change field names and values, obviously.

Jamie, this working fine! Thanks you so much!

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,083 views 13 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot