Timepicker plugin

[epixa]

The timepicker plugin should track the global time range in a service and expose to other plugins a programmatic client for manipulating the global time range. It should also expose an observable for the time range. We should expose a higher order timepicker component that is integrated with this service. The static timepicker UI component should be from EUI.

[epixa]

@elastic/kibana-discovery This is something the discovery team will own down the line, but it's one of the earlier things we need to build on the new platform to support greenfield app development, so the platform team will likely take a swing at this unless they get delayed or your time miraculously frees up in the coming months.

[epixa]

cc @elastic/kibana-platform

[timroes]

Since not losing the timepicker value is a common request (#4988, #18952) I wonder if keeping the time range is something that will be working within the concepts of the new platform for UI?

[epixa]

@timroes Yeah, my thinking was that the plugin would provide three things:

1. Ability to create/manage a time range state
2. A single shared time range state
3. Timepicker component that integrates with time range state

Plugins could then choose whether or not or to what extent they want to use 2.

[markwalkom]

This would be awesome, especially to allow visualisations that do "$metric this day/week/year"!

[woj-b]

Are there any workarounds for this at present? I found setting an interval in the Timelion query itself and setting all of the intervals to the smallest one used works, but this appears to be frowned upon, according to the documentation ("DO NOT USE")

[elasticmachine]

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

[ppisljar]

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.