Script Runner: Using JQL functions from other plugins

[Lukasz Chomin]

Hi,

I'm using in my script this JQL function from Profields plugin:

SearchService.ParseResult parseResult = searchService.parseQuery(ApplicationUsers.toDirectoryUser(user), "project in profieldsOperator(Language,\"=\",EN)")

When I run this script from Script Console everything works properly. But when I run it from script file as a scheduled service I get this error:

Script Runner [jira.profields.jql.JqlFunctionProfieldsOperator] Error JQL function profields when execute getValues() in class com.deiser.jira.profields.jql.JqlFunctionProfieldsOperator

What could be the reason for such error?

Thanks in advance for your help.

Best regards,

Lukasz Chomin

[JamieA · Accepted solution]

There is no user context in a service - you will need to set one with something like:

ComponentAccessor.getJiraAuthenticationContext().setLoggedInUser(User or ApplicationUser)

[JamieA]

but JQL functions should handle this more gracefully...

[Lukasz Chomin]

Hi Jamie,
Thanks for your prompt reply.
You are genius, adding this one line solved the issue.

BTW. Having this opportunity, may I transition an issue and add comment in the same step? Currently I'm doing this with two methods:

commentManager.create(issueManager.getIssueObject(issue.id), user, comment, true);
...
workflowTransitionUtil.setAction(1021);

and therefore I'm getting two notifications.
It would be much more user friendly to just get one.

Regards,

Lukasz

[JamieA]

This is a different question really... but wtu.setParams([comment: "my comment"]) might work... I've moved to using IssueService, but that has its own problems.