You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that the Job List page uses the Kibana time-picker to control its refresh rate, there are usability concerns around the how the end-user will know if their data is recent. This will hit existing end-users who are accustomed to more regular refreshing and new users as the list does not update as quickly in some circumstances. It is not obvious that the rate of refresh can be adjusted or that it is now timer based.
Two suggestions would help the end-user know if they are seeing recent info
A visual indicator showing a countdown to next refresh or time since last refresh
Ability to manually refresh the list without having to reload the whole page. This could be per job or all jobs.
@lcawl Can we please make it clear in docs that the refresh rate of the page is controlled by the Kibana time picker
ping @elastic/ml-ui
The text was updated successfully, but these errors were encountered:
Found in 6.4.0-SNAPSHOT (pre BC1)
Now that the Job List page uses the Kibana time-picker to control its refresh rate, there are usability concerns around the how the end-user will know if their data is recent. This will hit existing end-users who are accustomed to more regular refreshing and new users as the list does not update as quickly in some circumstances. It is not obvious that the rate of refresh can be adjusted or that it is now timer based.
Two suggestions would help the end-user know if they are seeing recent info
A visual indicator showing a countdown to next refresh or time since last refresh
Ability to manually refresh the list without having to reload the whole page. This could be per job or all jobs.
@lcawl Can we please make it clear in docs that the refresh rate of the page is controlled by the Kibana time picker
ping @elastic/ml-ui
The text was updated successfully, but these errors were encountered: