30 second timeout limit#166

I want to be able to run my Enhanced Search query for longer than 30 seconds so that I can get the full results I want without having to restrict my queries too much.

would be great to have it at least 2 min. and awesome to have 3 min.. This would help to acutally create the synced filter which helps a lot the cloud migration customers

+10[our customers] please extend the search timeout. most dev teams will have lot of issues to track and they will be stuck with maintainig the filters in SR rather than their own codes.

I can barely use the tool due to filter timeouts. Please implement this, or else we’ll find very little value in ScriptRunner.

The short timeout config seriously limits the value of the ‘enhanced search’. Side note: I can’t imagine any large enterprise customer that is being coerced to migrate to Jira Cloud would accept this either.

Thank you for all the feedback, we’re currently looking into ways to improve this and I will come back with updates - The Enhanced Search team

Any news in this one?

We are forced to use technical accounts for Enhanced Search since Adaptavist still does not support changing the ownership of shared filters. What do you think happens, when owners of enhanced search filters leave the company, eh?

Because of this limitation ScriptRunner in our setup becomes pretty much unusable: apart from the limitation in obtaining results immediately, very often it’s also not possible to foresee if a subquery set of results will exceed the limit in the future, so saving a SriptRunner enhanced filter and e.g. using it in a dashbord has become unreliable in Jira Cloud.

Adaptavist, Is there a different issue logged or is it all one in the same, that besides the 30 second timeout limitation, The background sync operation consistenly fails to run in the backround when a user has several (Had an open ticket with you all, but due to the complexity of the filters, it is hard to provide a general range of how many filters is too many) enhanced search filters, causing, plans, reports and dashboards where these filters are used (anywhere the filter is used), to be out of date.

Expecting users to go in manually everyday and sync their filters is an unreasonable ask.

How can this background sync be improved to run consistently?

This is a huge problem for the organization and has us looking for other products to solve our enhanced searching needs.

Can you please advise

It feels like the background sync performance and dependability is critical enough to be it’s own ticket to me. We have built out a large array of dashboards using advanced filters, and not being able to trust that the background operations and updates are working as expected has also started us thinking about alternative solutions.

Jason, I just created https://scriptrunner-for-jira-cloud.nolt.io/260 can you comment and vote there. Thank you!

extending to what Bonnie Lopes mentioned above, that we’re a large organization and we have complex JQL on ScriptRunner Enhanced Search. To use ScriptRunner Enhanced Search properly and get results as expected, there should not be any time limits unless the query takes more than 5 minutes to run. Most of our ScriptRunner Enhanced Search filters takes somwehere between 1 to 2 mins and this 30 seconds timeout and background sync not working because of that probably is not working for us.

Enhanced Search team - Thank you for updating the timeout to 2 minutes but we still see this message “The query may take up to 1 minute and 30 seconds to complete. Searches will time out after 30 seconds.”
Should you update the message as well ?

Apologies about that @Buddhadeb.paul , please let us know if that message is something that you’re still continuing to see as we had thought we had updated this with the new change!

Thanks for your feedback @Jason.cole and @Bonnie.lopes regarding background syncing. We’ll take this on board and will update on the separate Nolt feature should there be any updates on it!

@Gli : I still see the message as of today.
“The query may take up to 1 minute and 30 seconds to complete. Searches will time out after 30 seconds.”