[Maps] Filters applied to map visualization not preserved when added to dashboard

[patricklucas]

Kibana version: 7.10.2

Elasticsearch version: 7.10.2

Original install method (e.g. download page, yum, from source, etc.): Docker

Describe the bug: If you save a map visualization with filters applied, then add the map to a dashboard, the filters are not applied. This is different from (as far as I can tell) all other visualizations, where if you save one with a filter, that filter is also applied when it is added to a dashboard (in addition to filters applied to the dashboard itself, unless that behavior is opted-out in the visualization)

Steps to reproduce:

1. Add the "Flights" demo data
2. Edit the "[Flights] Origin and Destination Flight Time" map visualization, adding a filter {"range": {"timestamp": {"gte": "now-1h"}}}, then save the visualization
3. Create a new dashboard and add the visualization

Expected behavior: The visualized data should be filtered as saved in the visualization

Screenshots (if relevant):

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[thomasneirynck]

hi @patricklucas, this is a known behavior.

This behavior in Maps is in alignment with other parts of Kibana (e.g. Lens), but inconsistent with the older visualization types like you mention.

cc @kmartastic

[kmartastic]

Thanks for raising this as an issue @patricklucas.
I think most customers would feel like the behavior in Maps and Lens, which does not persist the filters, is a bug.
I will look into it further.

[patricklucas]

Thanks for the replies @thomasneirynck / @kmartastic.

In my use case, the map (and all the other visualizations) each have a simple filter applied that bounds the dataset to a "correct" subset of data, based on how my data is modeled*, and then filters can be added on the dashboard itself to drill down across all of the visualizations.

*I'm using the pattern of writing a document for every state update in each "flow" I'm monitoring, each with "start" and "end" timestamps to indicate the time range they are relevant. When I write a new state update, I modify the previously-written document to have an "end" timestamp. The visualizations in my dashboard each apply a filter of "end timestamp does not exist", which narrows my view to only the latest state update for each "flow".

[kmartastic]

@thomasneirynck This is not the behavior in Lens. We should fix this in Maps.

[nreese]

Changing label from bug to enhancement since its working as designed, even if the design is not what some users expect.

[nreese]

Another thread showing how not carrying filter state from maps app to dashboard causes confusion - https://discuss.elastic.co/t/maps-with-multiple-layer-appear-not-to-work-as-expected/268959

[kmartastic]

We should change how this works in Maps.

[mornelsd]

This issue persists in v7.17.8 sadly...

[nreese]

This issue persists in v7.17.8 sadly...

Issue is resolved in 8.5.0 and up. Please update to one of those versions to resolve the issue.

In order to ensure stability, 7.17.x is only updated with critical security fixes. Resolving this issue can not be backported to 7.1.7.x because it does not meet this criteria.

[mornelsd]

This issue persists in v7.17.8 sadly...

Issue is resolved in 8.5.0 and up. Please update to one of those versions to resolve the issue.

In order to ensure stability, 7.17.x is only updated with critical security fixes. Resolving this issue can not be backported to 7.1.7.x because it does not meet this criteria.

Thanks Nathan