tast-track transition doesn't work after create

Hello,

this is driving me crazy. I created a post script function on the create transition, so that issues of one kind (you'll see in the screeshot) would be closed automatically after create (this is used for imported issues from another system, that have been already handled). The fast-track doesn't work under any circumstances. I tried almost everything. Attached you may find more info.

Best

Pujan

Post Function - Fast Track.pngScript Post Function - Fast Track.pngworkflow transitions.png

3 answers

btw I see this exception when I'm adding the condition, but I don't think it's relevant:

2016-02-08 14:49:35,679 http-bio-8080-exec-16 ERROR pziaie 889x764492x1 16j9kjc 192.168.159.97,127.0.0.1 /rest/scriptrunner/latest/canned/com.onresolve.scriptrunner.canned.common.StaticCompilationChecker [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: Could not initialize class com.onresolve.scriptrunner.runner.stc.ScriptCompileContext$ContextByName

java.lang.NoClassDefFoundError: Could not initialize class com.onresolve.scriptrunner.runner.stc.ScriptCompileContext$ContextByName

        at com.onresolve.scriptrunner.runner.stc.ScriptCompileContext.fromLabel(ScriptCompileContext.groovy:86)

        at com.onresolve.scriptrunner.runner.stc.ScriptCompileContext$fromLabel.call(Unknown Source)

        at com.onresolve.scriptrunner.canned.common.StaticCompilationChecker.getContextFromParams(StaticCompilationChecker.groovy:81)

        at com.onresolve.scriptrunner.canned.common.StaticCompilationChecker$getContextFromParams.callCurrent(Unknown Source)

        at com.onresolve.scriptrunner.canned.common.StaticCompilationChecker.doScript(StaticCompilationChecker.groovy:103)

 

 

The stack trace is an outstanding issue that should be fixed in the next version.

Your condition should be:

cfValues["Message Source"]?.value == "EFDIS"

Validator examples are at https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/validators/simple-scripted-validators.html#_validating_a_multi_select_option_is_selected.

Does this mean it should be

cfValues["Message Source"]?.value == "EFDIS"
but at the moment there is an issue and it doesn't work?

Yes, it should be that. The stack trace doesn't affect anything functionally, it should still work fine.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

369 views 6 0
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