We have a workflow that relies heavily on the send custom email post function functionality that script runner provides.
In the To Issue Fields: I specify a custom field which is a multi-user selector field and get the below error no matter if I specify one user or multiple.
v3.0.7 doesn't fix it.
Below the stack dump generated in logs when the post function is executed.
Exception in thread "Thread-71" java.lang.NullPointerException: Cannot invoke method split() on null object
at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:88)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:32)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at java_lang_String$split$6.call(Unknown Source)
at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.SendCustomEmail.getAddressesFromFields(SendCustomEmail.groovy:529)
at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.SendCustomEmail$getAddressesFromFields$3.callCurrent(Unknown Source)
at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.SendCustomEmail.getAllToAddresses(SendCustomEmail.groovy:460)
at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.SendCustomEmail$getAllToAddresses$2.callCurrent(Unknown Source)
at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.SendCustomEmail.constructMail(SendCustomEmail.groovy:298)
at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.SendCustomEmail$constructMail.callCurrent(Unknown Source)
at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.SendCustomEmail.sendMail(SendCustomEmail.groovy:317)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1207)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodOnCurrentN(ScriptBytecodeAdapter.java:78)
at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.SendCustomEmail.this$dist$invoke$1(SendCustomEmail.groovy)
at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.SendCustomEmail$1.methodMissing(SendCustomEmail.groovy)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaClassImpl.invokeMissingMethod(MetaClassImpl.java:933)
at groovy.lang.MetaClassImpl.invokePropertyOrMissing(MetaClassImpl.java:1256)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1209)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1016)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:66)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141)
at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.SendCustomEmail$1.run(SendCustomEmail.groovy:354)
at java.lang.Thread.run(Unknown Source)
Hi Roy... long time. I can only see that problem happening if the custom field is empty... which is bad enough in itself. There is a comment: "// todo: need null check here".
I'm surprised this hasn't come up before though, if it's as simple as it looks. But that line is in a code block that only happens for single or multiple text CFs. Are you specifying the custom field by name or ID? If by name, do you have multiple custom fields with that name?
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.