-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Canvas] Customizable time picker #33867
Comments
Pinging @elastic/kibana-canvas |
We're up against the wall with this issue and some Canvases we'd like to deploy to the enterprise, we need Ideally it takes the values from the Kibana advanced settings for timepicker quick ranges as mentioned, different folks' data and use cases differ. |
If this isn't already in the plan, can we add an option to make the Canvas timepicker store the last selected time range as a browser cookie? Currently, when the timepicker is changed, it changes the time range for everyone using the canvas. So for instance, user1 sets the timepicker to "Last 7 days", user2 opens the same canvas and sets the timepicker to "Last 30 days". User1 hits the refresh button and the timepicker changes to "Last 30 days". The desired functionality from our perspective should be not to overwrite user1's setting and to leave it at "Last 7 days". |
I'm having similar issue regarding Canvas timepicker. A default range for all new user sessions with ability to change on per user session basis would be ideal |
This is a pretty common request that I imagine will be even more prominent when we introduce filter groups. It'd be great to generally improve the timepicker (maybe re-using EUI super date picker), we should provide a way to customize the date picker. Minimally, defining the the "quick options" available. Everyones data set is different, these should be completely customizable.
Optionally, it'd be nice to turn on and off quick picks, relative selection, absolute, etc. These options should be both available in the UI and the expression language. I do not think we should introduce without having support in the UI.
cc: @grabowskit @ryankeairns @shaunmcgough
The text was updated successfully, but these errors were encountered: