-
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
[Discover] Refresh interval hidden in non time series data sets #102132
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
Just want to add a note that I think having auto-refresh on non time-based indices is probably a valid case. |
|
I really liked the solution @cristina-eleonora drafted a while ago , this would solve this issue FYI @elastic/kibana-design |
FWIW, there are split opinions (pun intended) on the split button approach. That aside, I do like having the options closer to the button and we could simply use a second, icon-only button in lieu of a true split button design. |
Re-adding our fix it week label. When autorefreshing the data, and switching to an data view without time picker, auto refresh should be stopped. If our time picker would be ready to just provide the auto-refresh functionality for data views without time field, this behavior can be changed. But currently, a such a change causes a state that the user can only change by tweaking the URL. |
Description
If you select an automatic refresh interval in Discover for a time series data set, and then change to a non time series data set, the data set will still refresh as per your setting, and there is no way to change it back unless you re-open the time series data set. This is due to the fact the date picker is hidden in non time series data sets. The behavior is noticed in this case when you have a row expanded. The row is collapsed every time the data is refreshed.
Reason
This is being filed as a bug, because it's impacting users that switch between index patterns of time series and others.
The text was updated successfully, but these errors were encountered: