In a JIRA workflow, I would only like to a require a Custom Field called "Changelist #" when the Resolution Type of the issue is "Fixed"
I've tried using the following snippet as my condition for my ScriptRunner simple scripted validator, but it is not functioning as intended:
issue.resolutionObject?.name != "Fixed" || cfValues['Changelist #']
I'm using this documentation, but have a feeling I'm not referencing my Custom Field correctly.
Any help is appreciated!
The logic seems valid. Breaking it down:
You want the entire statement to be true in these two cases, where the resolution ISN'T "Fixed" OR where the resolution IS "Fixed" AND "Changelist #" is populated. So the code for that would be
issue.resolutionObject?name != "Fixed" || (issue.resolutionObject?name == "Fixed" && cfValues['Changelist #'] != "")
which reduces down to what you have above. It uses what the script runner documentation you linked to references as "Groovy Truth"
However, if you wanted to see if someone actually enters something in the "Changelist #" field during the actual transition, you have to do something additional to check for that. Something involving using the issue and originalIssue objects along with getting the custom field value in a different way.
Your condition looks fine, but could you clarify your workflow? Does the issue already have a resolution of "Fixed" and you want to add a validator for when someone changes the resolution to something else FROM "Fixed"? Or this is validator for when someone changes the resolution from something TO "Fixed"? I assume it's the latter.
cfValues['Field Name'] should be the correct way to check whether a field is empty or not. Have you remembered to publish your workflow after adding this validator? Have you ensured that the field 'Changelist #' is actually completely empty?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG