Script Runner: Field 'issueFunction' does not exist

[Matthias]

I have just installed the Script Runner plugin (version 2.1.15) in my Jira (v6.0.8#6109-sha1:57cf099)

Whe I do a search using a script JQL function like

issueFunction in linkedIssuesOf("labels = 'XXXX'", "Contains")

I get the following error:

Field 'issueFunction' does not exist or you do not have permission to view it.

I've already tried a re-indexing and re-login.

I checked at AddOns->ScriptRunner->Scripted JQL functions and all the functions are enabled.

Any help here?

[Matthias · Accepted solution]

Restarting Jira solved the issue. The source is still not clear.

[Nicolai Klose]

Hey guys & girls

we get the same message with the trial version of scriptrunner. In our cloud jira the customfield is missing, i think its not created on plugin installation. Reinstalling the plugin did not help.

Anyone had this problem?

[Anatolijs Tarasovs]

This is an old thread, but if someone encounters the issue again, then adding global scheme context to the issueFunction field solved it for us.

issueFunction.png

[MB]

The error tells you there is a problem with your Custom Field named "issueFunction". Btw, what did you want your SQL to return? Currently you are checking if the value of your Custom Field is in the list of Issues, which implies that your Custom Field type is Issue (i.e. you have created a new Custom Field Type). Is that really the case?

P.S.
If I understand correctly, you have read the article about Scripted JQL Functions, which means you're using your jql inside a Script Runner plugin, right? The syntax of those jql queries is a bit different than the syntax of the original JIRA JQL queries, which means you need to use that query inside a Script Runner and not in the JIRA search.

[Matthias]

the filed comes from the Script Runner plugin and should be added automatically during installation. The query above lists all issues, which a part of an issue with a particular label and works fine in a different installation using this plugin.

[MB]

I see, let me check again to see if I didn't understand it wrong.

Update: Just ignore my previous answer and try reading this question. It suggests to re-install the Script Runner.

[JamieA]

Try disabling then enabling the plugin...

[Vera Henrichs]

Disabling adn enabling worked for me.

[stephanie]

sorry - replied to wrong thread