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

Workflow validator not executed

Robert Krause

I am running Jira 6.3.3 and the latest Version of Script Runner. I am trying to run a custom validation script on a workflow but it seems not be executed as nothing happens and there are no entries in the log file, even if the script contains syntax errors. I have also tried running the example validator from the website, with the same result. Any suggestions what could be the problem or where to look for further information?

Accepted answers

All comments

Tsol

Could you provide your code so we check more in details?

JamieA

Make sure the workflow is published, and associated with the project/issue type you are testing with.

Robert Krause

@KostasTo narrow it down I reduced the code to a bare minimum. My aim was to see if it runs, by having a validator that always fails. I tried a simple

false

which seemed to have worked for older versions and the example from the documentation

import org.apache.log4j.Category
import com.opensymphony.workflow.InvalidInputException
 
log = Category.getInstance("com.onresolve.jira.groovy.example.testValidator")
log.debug("Condition testValidator script running")
 
invalidInputException = new InvalidInputException("Validation failure")

Neither the validation fail nor the log message is shown.

@JamieI double checked it with a collegue.

Tsol

The following script

import org.apache.log4j.Category
import com.opensymphony.workflow.InvalidInputException
 
log = Category.getInstance("com.onresolve.jira.groovy.example.testValidator")
log.debug("Condition testValidator script running")
 
invalidInputException = new InvalidInputException("Validation failure")

is executed for me. I got the log and transition was not executed.

Are u sure that you have followed the steps in order to have the custom script validator executed?

In order to make it work you have to:

Create a file with the above code
Add it to a directory of your server
Add the file path to your workflow

Hope that helps

Alexey_Rjeutski__Polontech_

Could you provide full information how do you add this condition to a workflow?

JamieA

Could just add a screenshot. It really depends if you are using "custom validator" or "simple scripted validator". They work differently. "false" is fine for the latter. For the former, try finishing your script with:

throw new InvalidInputException("Validation failure")

what version of SR are you using?

Robert Krause

I am using a Custom Validator and SR version 3.0.4

I am using an absolut path to the script file and tried to run it as inline script as well. Running it from a file I just noticed this message in the log:

/secure/CommentAssignIssue.jspa [onresolve.scriptrunner.runner.ScriptRunnerImpl] Add a script root for this path: /path/to/my/file/script.groovy

Do you have any suggestions how to resolve this?

Radu Dumitriu

Are you sure you published your workflow? Just making sure ....

Robert Krause

@RaduYes I am.

Radu Dumitriu

... and you are on the correct issue type, if WF was not published for all issue types ... ?

Alexey_Rjeutski__Polontech_

And workflow scheme with proper workflow attached to project

JamieA

Does using:

throw new InvalidInputException("Validation failure")

work?

Robert Krause

Yes it is.

Yes it is. I am using a default workflow in an out of the box Jira with Script Runner.

Manuel Kummerländer

Yes, "throw" works for me. (I have the same problems as Robert)

import org.apache.log4j.Category
import com.opensymphony.workflow.InvalidInputException
  
log = Category.getInstance("com.onresolve.jira.groovy.example.testValidator")
log.debug("Condition testValidator script running")
  
throw new InvalidInputException("Validation failure")

JamieA

What version of the plugin are you using? I think I may have broken that backwards compatibility in one of the most recent releases.

Radu Dumitriu

Blame it on the developer, right.

Manuel Kummerländer

@jamie I use Jira 6.3.4 and Script Runner 3.0.4.

Robert Krause

Okay. Turns out, I tested the throws variant only from a file not as an inline script, which works file.

Thank you for your help.

I am still curious what to do about the log message, if I try to run a custom script from a file:

/secure/CommentAssignIssue.jspa [onresolve.scriptrunner.runner.ScriptRunnerImpl] Add a script root for this path: /path/to/my/file/script.groovy

JamieA

"throw new InvalidInputException" works fine for me fron file and inline script. In 3.0.5:

invalidInputException = new InvalidInputException

will also work (from both).

JamieA

@Radu... it could be any member of the massive development team. But when I found out who, they'll be sorry....

Radu Dumitriu

@Jamie- be merciful

http://9gag.com/gag/ad604MN

Alexey_Rjeutski__Polontech_

99 little bugs in the code

Take one down, patch it around

117 little bugs in the code

Welcome!

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

Quick Links

Find more posts tagged with

jira

addon-com.onresolve.jira.groovy.groovyrunner