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

Simple Scripted Validator triggers error, but keeps triggering even after field is filled out

Kathryn Allison

I have a simple scripted validator I want to validate whether a field it filled out based on another field's value:

cfValues['Implementation Method']?.getValue() == "Premise" || cfValues['Implementation Method']?.getValue() != "Premise" && issue.projectObject.key != "ELM"

When "Premise" is the value in the custom field it lets me move the workflow. When "Premise" is not the value, it throws a validator against Due Date (as intended), but keep throwing it even after I fill out Due Date field.

Also, I need this to be expanded to 3 other projects, and wasn't positive on how to do that.

Thanks in advanced.

Accepted answers

JamieA

Use brackets.

Use the condition tester with asserts, that should make it clear.

https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-ConditionTester<br< a="">>https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-PowerAssertions

All comments

Sir Be

is it A or B and C

or (A or and C

or A or (B and C) ?

Kathryn Allison

A or (B and C)

Sir Be

Does the adding of the brackets to the code make any difference?
(Never know)

To 'debug': add some println's

println cfValues['Implementation Method']?.getValue()

println cfValues['Implementation Method']?.getValue() == "Premise"

....

And check your log, maybe it helps?

Kathryn Allison

No, it didn't. The validator is passing the erroring properly, but once I fill out the field being validated against, it still throws the error message. If I replace Implementation Method with a different custom field/value it works correctly.

JamieA

Use brackets.

Use the condition tester with asserts, that should make it clear.

Kathryn Allison

There's nothing wrong with the script. Even testing against a simple line I'm having the same issue: the script throws the validation error against the Due Date field, but keeps throwing it even after I fill out due date. If I use a different custom field, it works how I expect it to. Both custom fields are of Select List type.

JamieA

I don't understand where Due Date comes in to this. Can you attach a screenshot?

If you've put the error against Due Date it will go against that field, but if that field is not in the validator it has nothing to do with whether the condition passes.

Is your objective to make the due date required depending on some other conditions?

If so you should do

cfValues['Due Date'] || ! (your current clause)

that is, the due date is required unless your current clause is true.

Kathryn Allison

Due Date is not a custom field, but a system field, would cfvalues['Due Date'] still work for system field? I did put it against the field without the field in the validator, and I have done so in the past and it worked fine. The current one also works the same way with a different custom field then I am using currently.

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

jira

simple-scripted-validator