[8.x] [Security Solution][Alert Flyout] Update entity insight badge to open entity flyouts (#208287)#210476
Merged
christineweng merged 1 commit intoelastic:8.xfrom Feb 11, 2025
Conversation
… entity flyouts (elastic#208287) ## Summary This PR updates the cloud insights in entity section to open to entity flyout. When examining the insights (for example, the host is shown to have 50 alerts, instead of opening the preview, and user click on the details and go to respective tabs, this PR updated the behavior to open the details tab via 1 click. The goal is to reduce friction for users during investigation. Feature flag: `newExpandableFlyoutNavigationEnabled` When flag is off: - Click on alert count should open timeline (if user has timeline privileage) - Click on misconfigurations and vulnerabilities badge should open host/user preview https://github.com/user-attachments/assets/23e0cc40-129d-4e75-b5be-26a49dcad710 When flag is on: - Click on count badges should open the respective entity flyout and the insights details tab https://github.com/user-attachments/assets/5dfc39b7-edae-4b76-9a3a-79326337cb3b ### Checklist - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) (cherry picked from commit 6e61f52) # Conflicts: # x-pack/solutions/security/plugins/security_solution/public/flyout/document_details/shared/components/alert_count_insight.tsx
3 tasks
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
|
PhilippeOberti
approved these changes
Feb 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
mainto8.x:Questions ?
Please refer to the Backport tool documentation