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?