ScriptRunner Cloud issueFunction not working in Enhanced Search after installation and sync

[confluenceadmins]

Hello,

I’m using Jira Cloud and I have just installed ScriptRunner and completed the manual metadata sync.

ScriptRunner Enhanced Search is enabled, but I cannot get ScriptRunner JQL functions to work.

Whenever I try to run a search using issueFunction (for example issueFunction in hasLinks() or issueFunction in linkedIssuesOf("project = xyz")), I immediately get the error: “Searching failed. Please try again later.” In some cases, after clicking Search, it also shows: “The field 'issueFunction' does not exist or you do not have permission to view it.”

Standard JQL works correctly, so Jira itself and issue links are working as expected.

Is there any additional configuration required after installation and manual sync to enable issueFunction in Jira Cloud, or what could it be?

Thanks in advance for any help!

[Germán Morales _ Hiera]

Hi @confluenceadmins, two things to check.

ScriptRunner Cloud is built and maintained by Adaptavist, not Atlassian. Their issueFunction JQL extensions depend on their app being properly registered with your Jira instance, and the metadata sync needs to complete fully before the functions become recognized. The error "field 'issueFunction' does not exist or you do not have permission to view it" is consistent with the JQL engine not seeing the registered function at search time.

A few things worth verifying:

• Atlassian moved Jira search to a new Enhanced JQL endpoint over the past year. ScriptRunner's custom issueFunction queries had to be updated to support that endpoint. Confirm in ScriptRunner's admin section that the app is on the latest version compatible with Enhanced Search.
• Re-trigger the metadata sync from ScriptRunner's admin page even if the initial one ran. The first sync after install sometimes completes partially.
• Check that your user account has the permissions ScriptRunner expects. The "do not have permission" wording in the error suggests the engine recognized the field but rejected the actor.

If after those checks it still fails consistently, this is something Adaptavist Support is best positioned to investigate since they own the function implementation.