Open kindsun opened 3 years ago
Pinging @elastic/kibana-gis (Team:Geo)
Pinging @elastic/kibana-presentation (Team:Presentation)
Maybe not a "bug" perse, but I do agree it is a real challenge.
Layers can have capabilities and depending on those capabilities, one or more features of the global Kibana-chrome is not applicable.
Time-picker is a good example (= this ticket). Another one in the context of Maps is that the map can consist of layers that are not filterable/queryable. For those it would not be relevant to show the query and/or filter bar. https://github.com/elastic/kibana/issues/91865
Adding presentations-team label, since challenge is similar there. cc @clintandrewhall
The legend has a clock icon next to layers filtered by time picker to clearify which layers are filtered by the time picker
@nreese Good point, but it's an inclusive-only indicator. It helps you differentiate when you have multiple layers, some of which are controlled by the Time picker and some of which aren't. When you have a map with just one or more index patterns without time fields, it just looks like this:
So really no indication that the time filter isn't useful or doesn't apply to the layer.
So really no indication that the time filter isn't useful or doesn't apply to the layer.
In the case where no layers are using the time picker, then it should be off like in visualizations.
Linking to lens issue about what to do about time picker when there is no default time fields https://github.com/elastic/kibana/issues/72502
Index patterns without a time field enabled cause the timepicker to show up as
off
in visualizations since limiting data by time isn't applicable:In Maps it's a little trickier since there can be multiple index patterns present, some of which might have a time field and some of which don't. This means when a layer is added based on an index pattern with no time field, the Timepicker still appears but has no effect on the index pattern layer(s) without time fields. This is however consistent with Dashboard which has a similar challenge of managing multiple visualizations deriving from different index patterns:
Ultimately, Maps is consistent with Dashboard, so this is very likely not a bug, but ideally there would be some indication to the user that the Timepicker isn't relevant for some or all layers present without Time fields.