Displaying ScriptRunner Enhanced Search Queries in JQL

Question

Hello,

Since our migration to JIRA Cloud, we have had to save our ScriptRunner Enhanced Search queries as filters before using them in JQL queries and JIRA dashboards.

As a result, the JQL now references the filter name rather than displaying the actual ScriptRunner query. While I know the query behind each filter as the creator, other users in the organization need to perform additional steps to identify the underlying query (Apps -> ScriptRunner Enhanced Search -> search for the exact filter name).

Is there a way to display the ScriptRunner Enhanced Search query itself in the JQL field instead of the filter name ?

Thank you for your help.

Gor Greyan · Accepted Answer

Hi @Guillaume Desgrippes

As far as I'm aware, this isn't currently supported in ScriptRunner for Jira Cloud.

In Cloud, Enhanced Search queries are designed to be saved as Enhanced Search filters, which are then referenced from Jira boards, dashboards, and JQL using the filter rather than displaying the underlying Enhanced Search query. I don't believe there's a native option to have the JQL editor expand the filter reference and display the actual Enhanced Search query instead of the filter name.

The Adaptavist documentation on Saved Filters explains how Enhanced Search queries are stored and shared:

https://docs.adaptavist.com/sr4jc/latest/features/scriptrunner-enhanced-search/scriptrunner-enhanced-search-jql-queries/saved-filters

If this would improve usability for your users, please raise it as a feature request with Adaptavist, as it would require a change to how Enhanced Search integrates with Jira Cloud.

Kristian Walker _Adaptavist_ · Accepted Answer

Hi @Guillaume Desgrippes, Thank you for your question. I can confirm that in Jira Cloud you can only use the issueFunction() JQL function provided by ScriptRunner on the Enhanced Search page as described in the documentation here currently. This is due to the way that Atlassian restricts how the JQL functions can interact with their infrastructure, meaning we must run them in a sandbox process. However, this does not mean that they cannot be used inside other filters or on filters for Agile boards. To use the functions in other filters, you may follow the steps outlined below. * Navigate to the enhanced search page and construct the filter you require using the JQL functions provided bv ScriptRunner. * Save your filter and share it with the users that are required to be able to see it. * Create the JQL search used by your board filter or quick filter and reference the saved filter using the syntax shown below which will return the results of your filter using the JQL functions provided by ScriptRunner. filter = "" I hope this helps. Regards, Kristian