After upgrading to JIRA 6.3.1 and Script Runner 3.0.1, our scripted JQL functions are failing to load.
We've reviewed the document on breaking changes in 3.0 and attempted to migrate the scripts. After scanning, a tooltip/popup says no additional scripts are added, and in the atlassian-jira.log we see an entry that the script file(s) 'failed to load/compile' with no additional detail.
As a test, we tried to create a function that does only returns null following the example provided (ABC.groovy), with no change.
Is there any undocumented gotches to the new format, or anything we can do to improve the debugging information on WHY it failed to load?
Any ideas would be appreciated, thanks.
package com.onresolve.jira.groovy.jql
import com.atlassian.crowd.embedded.api.User
import com.atlassian.jira.jql.query.QueryCreationContext
import com.atlassian.jira.util.MessageSet
import com.atlassian.query.clause.TerminalClause
import com.atlassian.query.operand.FunctionOperand
import org.apache.lucene.search.Query
class JQLTEST extends AbstractScriptedJqlFunction implements JqlQueryFunction{
@Override
String getDescription() {
"test JQL function"
}
@Override
List<Map> getArguments() {
[]
}
@Override
String getFunctionName() {
"testJQL"
}
def String subquery
@Override
MessageSet validate(User user, FunctionOperand operand, TerminalClause terminalClause) {
null
}
@Override
Query getQuery(QueryCreationContext queryCreationContext, FunctionOperand operand, TerminalClause terminalClause) {
null
}
}