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] Preview navigation in document details flyout #204292

Merged

Conversation

christineweng
Copy link
Contributor

@christineweng christineweng commented Dec 13, 2024

Summary

This PR enables navigation when an user is viewing an alert/event preview.

  • To see the new navigation, enable feature flag newExpandableFlyoutNavigationEnabled
  • This PR only covers navigations available in the alert/event preview. Links in host and user flyouts will be done in a separate PR

How navigation used to work:

  • When a document details flyout is open, many sections have nevigation links to open the details panel in the left
  • However, these navigations were disabled in a preview mode, and user is limited to stay in the original flyout context

Preview navigations now available

  • When the feature flag is on, navigation links is available
  • For example, an user is on an alert preview, and click on Entities, a new flyout will be opened (for the alert context) and the entities details section will be available.

Before
image

After
image

Screen.Recording.2024-12-13.at.5.12.45.PM.mov

Checklist

@christineweng christineweng added backport v9.0.0 Team:Threat Hunting Security Solution Threat Hunting Team release_note:feature Makes this part of the condensed release notes Team:Threat Hunting:Investigations Security Solution Investigations Team v8.18.0 labels Dec 13, 2024
@christineweng christineweng self-assigned this Dec 13, 2024
@christineweng christineweng requested a review from a team as a code owner December 13, 2024 23:14
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

Copy link
Contributor

@PhilippeOberti PhilippeOberti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

code LGTM and desk tested. In combination with the history functionality, this thing is awesome!

I left a comment, if you're making a push to the branch to solve the failing build, would you mind maybe renaming the few isEnabled variables to something a bit more clear like isNavigationEnabled or isLinkEnabled...? If you do this in the components directly (instead of in the hook) you shouldn't have to change any of the unit tests...

@christineweng christineweng enabled auto-merge (squash) December 16, 2024 20:33
Copy link
Contributor

@PhilippeOberti PhilippeOberti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for making the change to the isEnabled variable :)

@christineweng christineweng merged commit d638475 into elastic:main Dec 16, 2024
8 checks passed
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.x

https://github.com/elastic/kibana/actions/runs/12362533615

@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] Jest Tests #5 / useFleetServerUnhealthy should call notifications service if an error happen while fetching status

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
securitySolution 6410 6411 +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 14.7MB 14.7MB +452.0B

History

cc @christineweng

@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
8.x Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 204292

Questions ?

Please refer to the Backport tool documentation

@christineweng
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

christineweng added a commit to christineweng/kibana that referenced this pull request Dec 17, 2024
…astic#204292)

## Summary

This PR enables navigation when an user is viewing an alert/event
preview.

- To see the new navigation, enable feature flag
`newExpandableFlyoutNavigationEnabled`
- This PR only covers navigations available in the alert/event preview.
Links in host and user flyouts will be done in a separate PR

How navigation used to work:
- When a document details flyout is open, many sections have nevigation
links to open the details panel in the left
- However, these navigations were disabled in a preview mode, and user
is limited to stay in the original flyout context

Preview navigations now available
- When the feature flag is on, navigation links is available
- For example, an user is on an alert preview, and click on `Entities`,
a new flyout will be opened (for the alert context) and the entities
details section will be available.

**Before**
<img width="1483" alt="image"
src="https://github.com/user-attachments/assets/a8a21b86-21c1-48d4-ae4e-4ca5b337a2b0"
/>

**After**
<img width="1449" alt="image"
src="https://github.com/user-attachments/assets/2db865f3-3a31-440c-bc84-3003928c1f6a"
/>

https://github.com/user-attachments/assets/ae62b553-1ec9-4663-9ed3-ff20b2355061

### Checklist

- [ ] 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/packages/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

(cherry picked from commit d638475)

# Conflicts:
#	x-pack/plugins/security_solution/public/flyout/document_details/right/components/notes.test.tsx
#	x-pack/plugins/security_solution/public/flyout/document_details/right/components/notes.tsx
christineweng added a commit to christineweng/kibana that referenced this pull request Dec 17, 2024
…astic#204292)

## Summary

This PR enables navigation when an user is viewing an alert/event
preview.

- To see the new navigation, enable feature flag
`newExpandableFlyoutNavigationEnabled`
- This PR only covers navigations available in the alert/event preview.
Links in host and user flyouts will be done in a separate PR

How navigation used to work:
- When a document details flyout is open, many sections have nevigation
links to open the details panel in the left
- However, these navigations were disabled in a preview mode, and user
is limited to stay in the original flyout context

Preview navigations now available
- When the feature flag is on, navigation links is available
- For example, an user is on an alert preview, and click on `Entities`,
a new flyout will be opened (for the alert context) and the entities
details section will be available.

**Before**
<img width="1483" alt="image"
src="https://github.com/user-attachments/assets/a8a21b86-21c1-48d4-ae4e-4ca5b337a2b0"
/>

**After**
<img width="1449" alt="image"
src="https://github.com/user-attachments/assets/2db865f3-3a31-440c-bc84-3003928c1f6a"
/>

https://github.com/user-attachments/assets/ae62b553-1ec9-4663-9ed3-ff20b2355061

### Checklist

- [ ] 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/packages/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

(cherry picked from commit d638475)

# Conflicts:
#	x-pack/plugins/security_solution/public/flyout/document_details/right/components/notes.test.tsx
#	x-pack/plugins/security_solution/public/flyout/document_details/right/components/notes.tsx
@christineweng
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

christineweng added a commit that referenced this pull request Dec 18, 2024
…ut (#204292) (#204514)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Security Solution] Preview navigation in document details flyout
(#204292)](#204292)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-16T22:34:26Z","message":"[Security
Solution] Preview navigation in document details flyout (#204292)\n\n##
Summary\r\n\r\nThis PR enables navigation when an user is viewing an
alert/event\r\npreview.\r\n\r\n- To see the new navigation, enable
feature flag\r\n`newExpandableFlyoutNavigationEnabled`\r\n- This PR only
covers navigations available in the alert/event preview.\r\nLinks in
host and user flyouts will be done in a separate PR\r\n\r\nHow
navigation used to work:\r\n- When a document details flyout is open,
many sections have nevigation\r\nlinks to open the details panel in the
left\r\n- However, these navigations were disabled in a preview mode,
and user\r\nis limited to stay in the original flyout
context\r\n\r\nPreview navigations now available\r\n- When the feature
flag is on, navigation links is available\r\n- For example, an user is
on an alert preview, and click on `Entities`,\r\na new flyout will be
opened (for the alert context) and the entities\r\ndetails section will
be available.\r\n\r\n**Before**\r\n<img width=\"1483\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/a8a21b86-21c1-48d4-ae4e-4ca5b337a2b0\"\r\n/>\r\n\r\n**After**\r\n<img
width=\"1449\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/2db865f3-3a31-440c-bc84-3003928c1f6a\"\r\n/>\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/ae62b553-1ec9-4663-9ed3-ff20b2355061\r\n\r\n\r\n###
Checklist\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"d638475c6760b844f8ef928a21d382ef279566df","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","v9.0.0","Team:Threat
Hunting","release_note:feature","Team:Threat
Hunting:Investigations","v8.18.0"],"number":204292,"url":"https://github.com/elastic/kibana/pull/204292","mergeCommit":{"message":"[Security
Solution] Preview navigation in document details flyout (#204292)\n\n##
Summary\r\n\r\nThis PR enables navigation when an user is viewing an
alert/event\r\npreview.\r\n\r\n- To see the new navigation, enable
feature flag\r\n`newExpandableFlyoutNavigationEnabled`\r\n- This PR only
covers navigations available in the alert/event preview.\r\nLinks in
host and user flyouts will be done in a separate PR\r\n\r\nHow
navigation used to work:\r\n- When a document details flyout is open,
many sections have nevigation\r\nlinks to open the details panel in the
left\r\n- However, these navigations were disabled in a preview mode,
and user\r\nis limited to stay in the original flyout
context\r\n\r\nPreview navigations now available\r\n- When the feature
flag is on, navigation links is available\r\n- For example, an user is
on an alert preview, and click on `Entities`,\r\na new flyout will be
opened (for the alert context) and the entities\r\ndetails section will
be available.\r\n\r\n**Before**\r\n<img width=\"1483\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/a8a21b86-21c1-48d4-ae4e-4ca5b337a2b0\"\r\n/>\r\n\r\n**After**\r\n<img
width=\"1449\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/2db865f3-3a31-440c-bc84-3003928c1f6a\"\r\n/>\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/ae62b553-1ec9-4663-9ed3-ff20b2355061\r\n\r\n\r\n###
Checklist\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"d638475c6760b844f8ef928a21d382ef279566df"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204292","number":204292,"mergeCommit":{"message":"[Security
Solution] Preview navigation in document details flyout (#204292)\n\n##
Summary\r\n\r\nThis PR enables navigation when an user is viewing an
alert/event\r\npreview.\r\n\r\n- To see the new navigation, enable
feature flag\r\n`newExpandableFlyoutNavigationEnabled`\r\n- This PR only
covers navigations available in the alert/event preview.\r\nLinks in
host and user flyouts will be done in a separate PR\r\n\r\nHow
navigation used to work:\r\n- When a document details flyout is open,
many sections have nevigation\r\nlinks to open the details panel in the
left\r\n- However, these navigations were disabled in a preview mode,
and user\r\nis limited to stay in the original flyout
context\r\n\r\nPreview navigations now available\r\n- When the feature
flag is on, navigation links is available\r\n- For example, an user is
on an alert preview, and click on `Entities`,\r\na new flyout will be
opened (for the alert context) and the entities\r\ndetails section will
be available.\r\n\r\n**Before**\r\n<img width=\"1483\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/a8a21b86-21c1-48d4-ae4e-4ca5b337a2b0\"\r\n/>\r\n\r\n**After**\r\n<img
width=\"1449\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/2db865f3-3a31-440c-bc84-3003928c1f6a\"\r\n/>\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/ae62b553-1ec9-4663-9ed3-ff20b2355061\r\n\r\n\r\n###
Checklist\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"d638475c6760b844f8ef928a21d382ef279566df"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
JoseLuisGJ pushed a commit to JoseLuisGJ/kibana that referenced this pull request Dec 19, 2024
…astic#204292)

## Summary

This PR enables navigation when an user is viewing an alert/event
preview.

- To see the new navigation, enable feature flag
`newExpandableFlyoutNavigationEnabled`
- This PR only covers navigations available in the alert/event preview.
Links in host and user flyouts will be done in a separate PR

How navigation used to work:
- When a document details flyout is open, many sections have nevigation
links to open the details panel in the left
- However, these navigations were disabled in a preview mode, and user
is limited to stay in the original flyout context

Preview navigations now available
- When the feature flag is on, navigation links is available
- For example, an user is on an alert preview, and click on `Entities`,
a new flyout will be opened (for the alert context) and the entities
details section will be available.

**Before**
<img width="1483" alt="image"
src="https://github.com/user-attachments/assets/a8a21b86-21c1-48d4-ae4e-4ca5b337a2b0"
/>

**After**
<img width="1449" alt="image"
src="https://github.com/user-attachments/assets/2db865f3-3a31-440c-bc84-3003928c1f6a"
/>



https://github.com/user-attachments/assets/ae62b553-1ec9-4663-9ed3-ff20b2355061


### Checklist

- [ ] 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/packages/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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release_note:feature Makes this part of the condensed release notes Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team v8.18.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants