-
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
[Fleet] Agent activity flyout #140267
Comments
Pinging @elastic/fleet (Team:Fleet) |
@jen-huang @kpollich As discussed with Jen, created a separate issue for the Agent activity UI changes, separated stretch goals out. Please review. |
@kellyemurphy I have added this issue to UX Writing project board. We would like a review of UI copy on the design. Specifically, would love copy feedback on:
|
Update: #140510 completes the minimum requirements, reopened the issue as planning to add more tests. |
Could you please confirm whether the Thanks! |
@prachigupta-qasource the stretch goals are moved out to this issue and currently planned for 8.7. |
UI changes coming out of #141567
Given the changes of bulk actions, the execution of large agent batches are going to be async, so the users are not immediately notified of the action outcome.
In order to improve the UX, there is going to be a new Flyout added on Agent list, to show the progress of the user actions.
Figma designs
Minimum goals:
/action_status
endpoint added in [Fleet] moving action batching to async #138870Abort upgrade
button for Upgrade action (move existing Upgrade callout functionality)Agent activity
buttonStretch goals:
View agents
button that navigates to a filtered list of agents included in the selected actionChange schedule
button for Upgrade actionReview error log
button that navigates to Discover app to show relevant error logsShow more
button that loads more activity (10 more actions?)Jump to...
button that displays a datepicker to load activity of a selected day.Review errors
button in agent listScreenshots
The text was updated successfully, but these errors were encountered: