Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Scriptrunner errors after upgrading to 4.* version

Hi There,


We've updated to the latest available version of Scriptrunner for our 6.4.7 JIRA version and now I see errors in the log file:

2018-02-01 09:50:01,372 atlassian-scheduler-quartz1.clustered_Worker-1 ERROR automation [atlassian.scheduler.core.JobLauncher] Scheduled job with ID 'com.onresolve.jira.groovy.groovyrunner:EscalationService-job:-266997063' failed
groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method
Cannot resolve which method to invoke for [null] due to overlapping prototypes between:
[interface com.atlassian.crowd.embedded.api.User]
[interface com.atlassian.jira.user.ApplicationUser]
at groovy.lang.MetaClassImpl.chooseMostSpecificParams(
at groovy.lang.MetaClassImpl.chooseMethodInternal(
at groovy.lang.MetaClassImpl.chooseMethod(
at groovy.lang.MetaClassImpl.getMethodWithCachingInternal(
at groovy.lang.MetaClassImpl.createPojoCallSite(
at org.codehaus.groovy.runtime.callsite.CallSiteArray.createPojoSite(
at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallSite(
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(
at com.onresolve.scriptrunner.canned.jira.admin.EscalationService.runService(EscalationService.groovy:406) <+2> (
at java.lang.reflect.Method.invoke(
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce.invoke(
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(
at com.onresolve.scriptrunner.canned.jira.admin.EscalationService.execute(EscalationService.groovy:334)
at com.onresolve.scriptrunner.canned.jira.admin.EscalationService$execute$0.callCurrent(Unknown Source)
at com.onresolve.scriptrunner.canned.jira.admin.EscalationService.runJob(EscalationService.groovy:432)
at com.atlassian.scheduler.core.JobLauncher.runJob(
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(
at com.atlassian.scheduler.core.JobLauncher.launch(
at com.atlassian.scheduler.quartz1.Quartz1Job.execute(
at org.quartz.simpl.SimpleThreadPool$

I can't understand where they are coming from. 

Any help is appreciated, thanks. 


4 answers

Suggest an answer

Log in or Sign up to answer
1 vote
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 03, 2018

I seem to remember this cropping up a while ago, internally.  Try raising it with the SR team at

Appears to be from EscalationServices settings. Increased interval stopped errors from appearing in log file. However manual running does not produce any errors. 

Anyone? Any ideas? 

In Installed plugins there is only one version of scriptrunner:

ls installed-plugins/ | grep -i groo
AUG Leaders

Atlassian Community Events