Filter Sync Timeout Issue with ScriptRunner Enhanced Search

Richard A. Michaels

I have the following ScriptRunner Enhanced Search which is creating a sync timeout error with the corresponding Jira filter.
project = "MyProject” AND issueType = Epic AND status = "In Progress" and issueFunction not in epicsOf(Created >= startOfYear(-1) and issuetype in (Story, Task,Bug, Spike)) 

I'm also getting a Forge compatibility warning that the issueFunction query returns more than 1000 values and takes over 25 seconds to process. What can I do to optimize this query?

Habib__Plugio__

Hi @Richard A. Michaels

The likely cause is the subquery inside epicsOf. It has no project clause, so it matches every Story, Task, Bug and Spike created since January 2025 on the whole site. As far as I can tell, the outer project = "MyProject" doesn't narrow it. Adaptavist's docs treat each function call as its own "precomputation" with its own limits.

Scoping the subquery itself should help:

project = "MyProject" AND issuetype = Epic AND status = "In Progress" AND issueFunction not in epicsOf("project = 'MyProject' AND issuetype in (Story, Task, Bug, Spike) AND created >= startOfYear(-1)")

If the children live in other projects, list those projects in the subquery instead. Adding parent is not EMPTY to the subquery may cut it further. It skips work items that sit under no epic.

If it is still flagged: per the docs, the 1,000 results and 25 seconds apply per function call, not per filter. So splitting the date range into two calls joined with AND should work. One takes created >= startOfYear(-1) AND created < startOfYear(), the other created >= startOfYear().

I couldn't test this on a ScriptRunner instance. The limits are from Adaptavist's Forge migration docs, the rest is my reading of them.