Note on ScriptRunner, since 3.1.3 they added pagination to the JQL functions code :

All included JQL functions should now run in constant memory. Previously, certain functions such as linkedIssuesOf, when using against a very large number of issues, would consume too much memory.

see: https://jamieechlin.atlassian.net/wiki/display/GRV/ScriptRunner+3.1.3

Thanks David for reaching out. I have responded to the mail. Hopefully, we can get to the bottom of it

I should also note that ScriptRunner 3.x's "issueFunction in parentsOf()" function runs in nearly the same amount of time as JQL Trick 5.3.x's "issue in parent()" function. I would assume both options are affected by the same underlying JIRA limitation.

Hey jobinkk@gmail.com, I've sent you an email about this to see if we can discuss it further.

Hello Atlassian,

Is there any progress on this issue? Unfortunately, this has become a big problem for lot of our customers and there is nothing we can do in a plugin to tackle this. Disabling the plugins/jql functions will help stabilizing the system but that takes away the precious functionality too.

Given that JQL and searching is fundamental to the business for many customers, can we bump up the priority for this? Or, are there any other workarounds that you can suggest?

Appreciate all the help. We have seen improvements in the later versions of JIRA but none providing marked improvements. This one seems to be the key issue. Hopefully, you can get this in one of the upcoming minor versions and that will make searching in our favorite project management system all the more fun

As reported by Philip Schlesinger we have seen the exact same timeout issue on a kanban board using issue in parent("issuetype = task"))) with 6.3.15

Atlassian please fix.

Our JIRA instance was going down twice a week when users were running heavy queries and doubled when our PMO started sprint planning. Temporary workaround for us was to contact our heavy JQL users and modify their query/filters and asked them to run non peak hours.

BTW this is affecting 6.4.4

Using the parent() function from JQL Tricks, it's more than doubling the time for some of our Agile boards to load. Sometimes those boards report a timeout error.

Please fix this ASAP.

Atlassian,

Due to this issue we faced two sub-subsequent outages last week. Please see my following comment for more context, how JQL-T function kills our JIRA instance - https://answers.atlassian.com/questions/11452262/answers/13402580
JQL-T vendor responds us that nothing can be improved at plugin side.

This should not be "Suggestion" and instead of this it should be P1 bug in JIRA in consideration of the large JIRA instance. Atlassian market JIRA can be scaled beyond 500K issues, but due to this bug we can't scale.