majority of enhanced search queries time out

Craig Gering
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 23, 2019

Just installed scriptrunner for jira cloud.  Sync'd issues via mgmt console... but majority of queries time out with time out saying possibly subquery returned too many results... 

Example query:  issueFunction in epicsOf("resolution = unresolved")

fails.  But if i run it multiple times in a row, it succeeds on 4th or 5th try...

any hints?  without being able to run more interesting queries this search feature pretty useless.

2 answers

0 votes
Dennis Grochowski November 20, 2023

Years have gone by but this hasn't been fixed yet.

Other solutions already fixed this problem. Our organization is going to use the solution provided by Appfire, which works great.

Happy to hear if Adaptavist is going to fix this issue processing limit or timing out limit somewhen.

GL November 21, 2023

Hi there, I'm from the Adaptavist team! Our first line recommendation is to restrict the query e.g. by project, issue type etc, but I appreciate you may sometimes want to run broader queries. We're looking into solutions to allow you to run the query for longer and we'll start to look into it more sometime next year. Let me know if you have any further questions!

Dennis Grochowski November 21, 2023

I appreciate your answer and am glad that this post got your attention. Sadly the recommendation is not usable for any customer that has more than 100 issues in a project.

This is ridiculous expecting people to restrict their processing issues to that limit. In our environment where a project has 50k - 250k issues, we're relying on automation rules that do their work depending on the results that are needed coming from the queries. Easy queries with "linkedIssuesOf" are already running in a timeout. And if a query works, the performance is so bad, there are no words for it.

Since this is a problem with the app for years now, I don't expect any improvement but I'll be glad if you're able to prove me wrong.

Like # people like this
0 votes
Kristian Walker _Adaptavist_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 24, 2019

Hi Craig,

Thank you for your question.

I can confirm that the "Search parsing timed out. You probably have a subquery that returns too many issues." error which you are receiving indicates that the subqueries for the JQL functions returns too many issues.

Unfortunately, we can only execute queries for a maximum of 30 seconds before timing them out as well as being able to only fetch 100 issues at a time in order to inspect the "Epics" field.

In order to overcome this error, we would advise that you make your subquery more restrictive, so that it returns fewer issues. in order to complete within the timeout period. 

One way that you could look to restrict the query would be to look at limiting the query to only return the Epics inside a project or set of projects instead of returning all epics inside of the Jira instance. 

You can see more details on how the enhanced search functionality works inside of ScriptRunner for Jira Cloud in the documentation page here.



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events