Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Timeout using ScriptRunner

Hi,

 

when using the enhanced search of scriptrunner cloud I often run into the issue, that it raises the error message:

"Search parsing timed out. You probably have a subquery that returns too many issues."

Can anyone tell me what the limitations are and if it is possible to change them?

The query is actually running for about 10 seconds before the message is raised.

 

Thank you in advance for the answers

 

1 answer

1 accepted

0 votes
Answer accepted

Hi Jochen,

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 sub queries 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 overcome this error we would advise that you make your subquery more restrictive, so that it returns less 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 issues inside a certain project or to return only issues updated within a certain timeframe. 

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

If this response has answered your question can you please mark it as accepted so that other users can see it is correct when searching for similar answers.

Regards,

Kristian

Kristian, I have experienced the same problem with searches in my team. Is there any way to adjust the timeout limit to more than 30 seconds? I have tried to narrow down my search results but for some searches I just can't avoid it and need to be able to search across 24k jira issues. Is there a way to change this 30 second max limit?

Hi Jose,

I can confirm that unfortunately, it is not possible to increase the time out limit for the enhanced search functionality due to the restricted nature in which we execute the searches in a sandbox environment.

This means that you will need to restrict your query to return fewer issues and have multiple search queries if you need to search for a lot of issues.

Regards,

Kristian

What the f***k?

We have about 1000 issues in release, and want to filter them by different links or some other criteria — and you tell me that you can process only 100 issues?

What are you getting paid for?

Like # people like this

I was getting the error as well. I had created 4 filters in scriptrunner, and found if the Filter names were only one word with no spaces, versus a couple of words with spaces I would not get the error.

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you