[Maps] Allow Maps Time Slider to work in Dashboards 🗺️

[nicpenning]

Describe the feature:
Allow the map time slider control to live in any dashboard the map visualization lives.

In the Dashboard you don't have the time slider:

When editing the maps, you can see it:

Describe a specific use case for the feature:
As a Kibana dashboard user, I would like to use the time slider only for maps in the dashboard.

The current issue is that I would like to have a sliding time window just for the map in a large dashboard because the global time slider control is way to expensive.

From the community (https://elasticstack.slack.com/archives/CND4DUJ10/p1668086986678009?thread_ts=1667910788.945659&cid=CND4DUJ10):

The Time slider on the maps while editing controls just the data on the map.
So that time slider doesn't exist outside of editing the map which is strange.
The time slider control you can add to a dashboard controls the entire dashboard which is not efficient and is very performance heavy.
I simply want the time slider only on the map as described in the documentation and how it works when editing.

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[nickpeihl]

As of 8.5, Dashboard has a time slider control that mimics the Maps time slider but for all panels on the Dashboard. You would prefer the time slider to only adjust the map panel. Since the Dashboard time slider is expected to be the eventual successor to the Maps time slider, I think you would be served better by each panel having the option to ignore the time slider control. We have an issue to allow panels to ignore global filters, but maybe we should plan to extend that functionality to allow panels to specifically ignore time slider filters?

[nicpenning]

You would prefer the time slider to only adjust the map panel. - Yes

Since the Dashboard time slider is expected to be the eventual successor to the Maps time slider, I think you would be served better by each panel having the option to ignore the time slider control. - Not quite, since I only want to time slide on the map not the entire dashboard which can be very busy (lots of visualizations) which makes for painful user experience with loading times.

We have an #112328, but maybe we should plan to extend that functionality to allow panels to specifically ignore time slider filters? - Possibly, but then I would have to do the inverse and tell all visualizations to ignore the global time slider filter except the maps and then use that one which will work until I want to use the time slider on everything else. Might be tough handle all the use cases by relying on the new global time slider. A thought would be to giving the user the ability to select which visualizations the global time slider can apply to. For example, the default is global (filters on all visuals) or selected visuals (Maps, Tables, etc.. or by name/title).

I simply just wanted that little slider button in the Maps visualization when it's in a dashboard :) This is starting to increasingly get a bit more complicated haha!

[nreese]

This is starting to increasingly get a bit more complicated haha!

Yes, things get complicated quickly. The Map timeslider was intentionally disabled on Dashboard because it only filtered the map and we could not find a suitable mechanism to inform users that timeslider only effect the map and not the entire dashboard.

[ThomThomson]

I wonder if we should re-enable the time slider on maps in Dashboard now that there is a whole-dashboard version of the time slider. On conflict, we would use the normal Embeddable systems to ensure that the timeslice from the Map overrides the dashboard time slider, but at the moment this would be left implicit / not shown to the user.

Then later when we build out that filter explorer system we've been thinking of this conflict could be plainly exposed to the dashboard author.

[nicpenning]

This is starting to increasingly get a bit more complicated haha!

Yes, things get complicated quickly. The Map timeslider was intentionally disabled on Dashboard because it only filtered the map and we could not find a suitable mechanism to inform users that timeslider only effect the map and not the entire dashboard.

Haha! And as stated, this is the opposite of what I would have expected. Bringing this back but as a toggleable option would fit both use cases.

[ThomThomson]

Closing this in favour of #29749 which is currently blocked on #1547.

With these features implemented, Dashboard authors will be able to fully control which dropdowns and filters affect which panels. It would be trivial to set up a group with a time slider that affects only one map.

[nicpenning]

Sounds good, thanks @ThomThomson !