Skip to content
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

[Security Solution][Alert details] - bring back last alert status change to flyout #205224

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

PhilippeOberti
Copy link
Contributor

Summary

Over a year ago, this PR added some information to the alert details flyout, to show when an alert's status (closed, open or aknowledged) had been modified last and by which user.
Shortly after, this follow up PR removed the UI from the alert details flyout, as the information wasn't extremely important and was taking some valuable vertical space, pushing down below the Highlighted fields section, that users were finding very important.

A few months later, we added the ability to persist which of the top sections (About, Investigation, Visualizations, Insights and Response) were collapsed or expanded. That way the user wouldn't have to always collapse or expand sections they would often don't need.

This PR brings back the alert's last status changes to the About section, as the vertical space is no longer a big issues, because users can now collapse the entire About section.

If data is not present, the last change UI is not shown

Screenshot 2024-12-27 at 3 46 14 PM

If the correct data is shown:

Screenshot 2024-12-27 at 3 50 12 PM

How to test

  • have a few alerts in the alerts table
  • open the alert details flyout for one alert and change the status (button in the header)
  • verify that the last status change section is shown in the About section

Checklist

@PhilippeOberti PhilippeOberti added v9.0.0 release_note:feature Makes this part of the condensed release notes Team:Threat Hunting:Investigations Security Solution Investigations Team backport:version Backport to applied version labels v8.18.0 labels Dec 27, 2024
@PhilippeOberti PhilippeOberti requested a review from a team as a code owner December 27, 2024 22:37
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

@elasticmachine
Copy link
Contributor

elasticmachine commented Dec 28, 2024

💔 Build Failed

Failed CI Steps

Test Failures

  • [job] [logs] Jest Tests #5 / AddInferenceFlyout valid submission

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
securitySolution 6508 6509 +1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
securitySolution 21.4MB 21.4MB +3.8KB

History

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:version Backport to applied version labels release_note:feature Makes this part of the condensed release notes Team:Threat Hunting:Investigations Security Solution Investigations Team v8.18.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants