Scripted JQL functions showing Enabled when they are really Disabled

[Brent Webster]

Successfully installed ScriptRunner 2.1.3 into Jira 5.2.2 and I have my managers using versionMatch in the JQL queries -- they were quite happy.

I restarted Jira and then my managers started nagging me that versionMatch could no longer be found. From the Admin page, I selected "Scripted JQL Functions" and scrolled to versionMatch where it indicated it was enabled (i.e. enabled link greyed out and disable link enabled). I pressed the disable and then the enable links, and that resulted in versionMatch function being found and operational.

I really don't want to have to reenable these functions after every restart.

[JamieA · Accepted solution]

Strange - when you are able to restart without causing problems, can you record the full log from startup?

Actually shutdown, set the log level to DEBUG, then start up again. When it's started test versionMatch, if there is a problem then create an issue in https://jamieechlin.atlassian.net/browse/GRV including your log file.

[Brent Webster]

Let's close this question. If it shows up again, I'll gather more info.

[Brent Webster]

Jamie, the server as been restarted and I performed the simple JQL query:

project = xxx AND "Planned For" in versionMatch("13.2.*")

and a red dialog is displayed with the following message:

Unable to find JQL function 'versionMatch(13.2.*)'.

In the catalina.out, the following DEBUG messages are issued:

2013-06-12 16:47:05,683 http-bio-8080-exec-7 DEBUG ebreweb 1007x28832x1 1pj3zbu 142.133.244.66,127.0.0.1 /rest/issueNav/1/issueTable/ [jql.operand.registry.LazyResettableJqlFunctionHandlerRegistry] Unable to find handler for function 'versionMatch'.
Note: above message repeated 6 more times with the same timestamp.

Then I queried the JQL functions from the Admin page:

i.e. .../admin/groovy/ViewScriptedJqlFunctions!default.jspa

versionMatch File/url: com.onresolve.jira.groovy.jql.EntityMatch (View Source)

Operations: Delete Preview Enable Disable
Match the version name by reg exp

So I enabled it and all is well but why wasn't it enabled by default after the reboot?

[Brent Webster]

Jamie: Just restarted the server again and performed the same simple jql query. The following messages were in the catalina.out file:

2013-06-12 17:23:09,399 http-bio-8080-exec-21 WARN ebreweb 1043x509x1 15egmhq 142.133.244.66,127.0.0.1 /rest/api/1.0/menus/find_link [jira.jql.query.GenericClauseQueryFactory] There is no OperandHandler registered to handle the operand 'in' for operand 'versionMatch(13.2.*)'.
2013-06-12 17:23:11,406 http-bio-8080-exec-16 WARN ebreweb 1043x512x1 15egmhq 142.133.244.66,127.0.0.1 /issues/ [jira.jql.query.GenericClauseQueryFactory] There is no OperandHandler registered to handle the operand 'in' for operand 'versionMatch(13.2.*)'.
2013-06-12 17:23:11,830 http-bio-8080-exec-11 WARN ebreweb 1043x514x1 15egmhq 142.133.244.66,127.0.0.1 /issues/ [jira.jql.query.GenericClauseQueryFactory] There is no OperandHandler registered to handle the operand 'in' for operand 'versionMatch(13.2.*)'.
2013-06-12 17:23:11,832 http-bio-8080-exec-11 WARN ebreweb 1043x514x1 15egmhq 142.133.244.66,127.0.0.1 /issues/ [jira.jql.query.GenericClauseQueryFactory] There is no OperandHandler registered to handle the operand 'in' for operand 'versionMatch(13.2.*)'.
2013-06-12 17:23:11,932 http-bio-8080-exec-11 ERROR ebreweb 1043x514x1 15egmhq 142.133.244.66,127.0.0.1 /issues/ [jira.groovy.jql.ScriptedJqlFunction] Function scriptedFunction didn't have a data type, returning Issue. Possibly plugin not started yet

And querying the jql function status shows that it is enabled.

versionMatch File/url: bundle://103.0:1/com/onresolve/jira/groovy/jql/EntityMatch.groovy (View Source)

Operations: Delete Preview Enable Disable
Match the version name by reg exp

I disabled and re-enabled the versionMatch function and it now works.