-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable Kibana Auto Form Submit #29356
Comments
Pinging @elastic/kibana-app |
I am interested in this. |
@kdotson3263k that is a valid request, just wondering if you had a stop button that terminate the query from the UI will that be sufficient? or do you still won't to have manual submitting for queries setting ? |
Related: #7238 |
I just witnessed the pain this can cause a user first-hand while I was on a call. When queries are time-intensive the user experience is absolutely terrible and productivity plummets. As mentioned in the issue description, the ideal UX would be:
I think we can address this in a BWC manner by offering an Advanced Settings option for "Refresh Elasticsearch queries immediately" with a default value of
|
For Discover this was implemented recently #42036 |
It's such an obvious inconvenience. I don't understand why it hasn't been resolved yet. |
Discover supports this today: #42036 (advanced setting) @ruslan528 which experience are you hoping for this in? Dashboard controls? Visualization editors? |
It seems that this has been resolved. |
Describe the feature:
I would like an option to disable Kibana's automatic form submission.
Currently, when you navigate to the Discover/Dashboard/Visualization page, Kibana will automatically submit the form based on the default index or last search. In addition, forms will submit when a filter property is changed. when the time is updated, or a saved filter is opened.
I am suggesting an option in the settings to disable the automatic form submit and only submit the form when the user clicks the "search" button.
Describe a specific use case for the feature:
The use case is to save cycles on large datasets/queries and allow the user to make multiple changes to a query before the form is submitted.
Thanks for the consideration!
The text was updated successfully, but these errors were encountered: