search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.71k stars 8.13k forks source link

Saved Query - Link to the query instead of copying it (like in Saved Search) #82692

Closed odmby closed 7 months ago

odmby commented 3 years ago

After I apply a Saved Query to a visual/dashboard it basically only copies it and stays static. If I edit the original Saved Query, it won't get updated in the visuals/dashboards that use it. The current behavior makes it unusable to our needs and defies the purpose. For Saved Search it works as I would expect, but the downside is that it can't be applied on already existing dashboards or visuals (which we have a lot).

elasticmachine commented 3 years ago

Pinging @elastic/kibana-app-arch (Team:AppArch)

elasticmachine commented 3 years ago

Pinging @elastic/kibana-app (Team:KibanaApp)

lukasolson commented 2 years ago

cc @cchaos @stratoula

elasticmachine commented 1 year ago

Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)

drewdaemon commented 1 year ago

+1 https://github.com/elastic/integrations/pull/6954#issuecomment-1636027028

Also note that this is currently an indirect Lens feature gap as well since we don't support saved searches in Lens. So, there's no way to have a query state that can be shared among Lens visualizations where changes would be reflected everywhere.

From @MakoWish

Yeah, that is a huge one for us and one of the biggest reasons we are not using Lens more. We have quite a few dashboards where all visualizations are linked to Saved Searches, because the filtering done on the Saved Search is updated from time-to-time (list of specific servers, services, etc.). Having to update the filters on every single visualization is not feasible. With a Saved Search, there is one change, and all the dashboards and visualizations based on that Saved Search will automatically reflect that change.

Saving filters to the dashboard itself is not a good idea at all, because users frequently want to search for things on their own, or apply their own filters, and when they clear filters or the search bar, they lose the base filtering we need on the dashboard to begin with. We don’t want standard users to have the ability to clear those filters at all.

stratoula commented 7 months ago

Closing as duplicate of https://github.com/elastic/kibana/issues/126735

MakoWish commented 7 months ago

@stratoula ,

Just curious... why would you close an issue that is more than three years old for one that is not as old. Shouldn't older issues be prioritized? I would think close the newer one and keep this open.

stratoula commented 7 months ago

I am keeping the issue that I feel describes better the problem for the team to understand. We have them linked so nothing is lost.