-
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
Make Default Search in Discover Editable #155751
Comments
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
Hi @rgarcia89! By "default search definition" you mean a selected data view or an open saved search?
The default Data View can be changed via
Discover does not open any saved search by default unless its id was specified in URL. What link do you usually follow to navigate to Discover? In both cases, the state can be reset by pressing "New" link in the top nav. |
Hi @jughosta I am normally going via Analytics -> Discover to reach the Search. However after that I always have to click on Open on the top right and select there our default search, which comes with some pre-selected columns as well as filters. I was wondering if I somehow could get rid of this. |
Yes, Discover does not support selecting a default saved search yet. Thanks for your suggestion, @rgarcia89! As a workaround for now, please consider navigating via "Recently viewed" links in the left navigation panel or create a browser bookmark. |
Yeah that's definitely a faster way to reach it. However, I would really love to see the implementation of such a feature. |
Closing as duplicate for #7238 |
Describe the feature:
Currently every time you open discover a default search definition is loaded, which cannot be changed. I would like to request a change here. It would be nice to either modify the search or select a saved search as default one.
Describe a specific use case for the feature:
In my case I do not use the default loaded search definition, as it does not filter the relevant fields. I would expect not to be alone with that.
The text was updated successfully, but these errors were encountered: