-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[ML] Persisted state in the URL, improve browser history navigation #83033
Comments
Pinging @elastic/ml-ui (:ml) |
This was referenced Nov 11, 2020
This was referenced Nov 19, 2020
2 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It'd be beneficial for the user to have a possibility to bookmark certain pages and have a better navigation experience across the ML plugin. This meta issue listing the enhancements around the URL state and navigation experience.
When landing on the Anomaly Explorer or Single Metric Viewer pages replace the browser history instead of pushing to avoid double click when navigating back. (related issue [ML] Multiple clicks required to navigate back from SMV/Anomaly Explorer to jobs list #73261)
When landing on the Single Metric Viewer pages with
metric
as a function, use the parameter for the function description instead of defaulting to one with highest anomaly score ([ML] Persist URL state for Anomaly detection jobs using metric function #83507)Preserve on the Anomaly Detection jobs list page ([ML] Persisted URL state for the "Anomaly detection jobs" page #83149)
Selected filters
Pagination
Sorting
Data frame analytics jobs ([ML] Persisted URL state for the Data frame analytics jobs and models pages #83439)
DFA models ([ML] Persisted URL state for the Data frame analytics jobs and models pages #83439)
DFA Results view ([ML] Persisted URL state for Data Frame Analytics Exploration page #84499)
Single Metric Viewer and Anomaly Explorer ([ML] Persisted URL state for Anomalies table #84314)
The text was updated successfully, but these errors were encountered: