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

jOhn Simonson

Is there a way to check of a "non-custom" field has a particular value?

I want to make sure the "Resolution" is "Not an Issue", but the script

cfValues['Resolution'] like 'Not an Issue'

does not work - it also does not complain that 'Resolution' is apparently not in "cfValues".

Is there a construct available for referencing the "Resolution"?

Thanks - jOhn -

Accepted answers

jOhn Simonson

Actually exactly the opposite - the "Resolution" must be "Not an Issue".
To clarify (using our state names, which are irrelevant to the problem):
during a transition from "Verification" to "Cancelled",
the action "Set Issue to Cancelled" shall be possible only if "Resolution" is "Not an Issue".
I was using the

Workflow > Transition "Set to Cancelled" > Validator:
Build-in Scripts: Simple scripted validator: "Has a custom field equal to"

but since "Resolution" is not a custom field, this was not working.

I was hoping for a simple way to access the value of "Resolution", and your code did the trick after changing it to

issue.resolution?.name == 'Not an Issue'

Thanks - jOhn -

All comments

Tsol

if i get it right you want to have a validator that will be evaluated to true only if issue resolution is not "Not an issue"

Then you have to add the following code in transitions that you set the resolution

issue.resolution?.name != 'Not an Issue'

jOhn Simonson

Workflow > Transition "Set to Cancelled" > Validator:
Build-in Scripts: Simple scripted validator: "Has a custom field equal to"

but since "Resolution" is not a custom field, this was not working.

I was hoping for a simple way to access the value of "Resolution", and your code did the trick after changing it to

issue.resolution?.name == 'Not an Issue'

Thanks - jOhn -

Tsol

In a different approach, since the transition accepts only one resolution, you could just add a post function that set the resolution to "Not an Issue" instead of using a validator.

jOhn Simonson

I guess the idea is to make the user really aware of what s/he is doing when cancelling an Issue after it has already been "integrated" and "verified" (those are the transitions we have after "opened").

I had also thought of that type of post function, but the stakeholders went with the validator.

Welcome!

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

Quick Links

Find more posts tagged with

jira

validator

simple-scripted-validator