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] Update footer link in rule preview to go to rule details page #195806

Merged
merged 3 commits into from
Oct 10, 2024

Conversation

christineweng
Copy link
Contributor

@christineweng christineweng commented Oct 10, 2024

Summary

Currently, the rule preview footer will open the rule flyout. Although this behavior is consistent with other previews (host, user, alert etc.), the rule flyout does not provide additional information for users. This PR updates the footer go to rule details page instead.

Screen.Recording.2024-10-10.at.11.56.45.AM.mov

Checklist

@christineweng christineweng added release_note:skip Skip the PR/issue when compiling release notes v9.0.0 Team:Threat Hunting Security Solution Threat Hunting Team Team:Threat Hunting:Investigations Security Solution Investigations Team backport:prev-major Backport to (8.x, 8.17, 8.16) the previous major branch and other branches in development v8.16.0 labels Oct 10, 2024
@christineweng christineweng self-assigned this Oct 10, 2024
@christineweng christineweng requested a review from a team as a code owner October 10, 2024 16:59
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

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.

as much as I don't like us making this change, the code looks good and desk testing works fine!
Thanks for jumping on this so quickly

@christineweng christineweng enabled auto-merge (squash) October 10, 2024 18:22
@christineweng christineweng merged commit a397bb7 into elastic:main Oct 10, 2024
41 checks passed
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.15, 8.x

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

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Async chunks

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

id before after diff
securitySolution 20.6MB 20.6MB -355.0B

History

cc @christineweng

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Oct 10, 2024
…details page (elastic#195806)

## Summary

Currently, the rule preview footer will open the rule flyout. Although
this behavior is consistent with other previews (host, user, alert
etc.), the rule flyout does not provide additional information for
users. This PR updates the footer go to rule details page instead.

https://github.com/user-attachments/assets/6de03775-b1a4-41b9-b233-7817d6cca8ec

### Checklist

- [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

---------

Co-authored-by: Jan Monschke <[email protected]>
(cherry picked from commit a397bb7)
@kibanamachine
Copy link
Contributor

💔 Some backports could not be created

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

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

Manual backport

To create the backport manually run:

node scripts/backport --pr 195806

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Oct 10, 2024
… rule details page (#195806) (#195833)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Security Solution] Update footer link in rule preview to go to rule
details page (#195806)](#195806)

<!--- Backport version: 9.4.3 -->

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

<!--BACKPORT
[{"author":{"name":"christineweng","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-10-10T21:59:54Z","message":"[Security
Solution] Update footer link in rule preview to go to rule details page
(#195806)\n\n## Summary\r\n\r\nCurrently, the rule preview footer will
open the rule flyout. Although\r\nthis behavior is consistent with other
previews (host, user, alert\r\netc.), the rule flyout does not provide
additional information for\r\nusers. This PR updates the footer go to
rule details page
instead.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/6de03775-b1a4-41b9-b233-7817d6cca8ec\r\n\r\n\r\n###
Checklist\r\n\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\r\n\r\n---------\r\n\r\nCo-authored-by: Jan Monschke
<[email protected]>","sha":"a397bb72d52e865d0f44c6983bf01c85875251e8","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat
Hunting","Team:Threat
Hunting:Investigations","backport:prev-major","v8.16.0"],"title":"[Security
Solution] Update footer link in rule preview to go to rule details
page","number":195806,"url":"https://github.com/elastic/kibana/pull/195806","mergeCommit":{"message":"[Security
Solution] Update footer link in rule preview to go to rule details page
(#195806)\n\n## Summary\r\n\r\nCurrently, the rule preview footer will
open the rule flyout. Although\r\nthis behavior is consistent with other
previews (host, user, alert\r\netc.), the rule flyout does not provide
additional information for\r\nusers. This PR updates the footer go to
rule details page
instead.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/6de03775-b1a4-41b9-b233-7817d6cca8ec\r\n\r\n\r\n###
Checklist\r\n\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\r\n\r\n---------\r\n\r\nCo-authored-by: Jan Monschke
<[email protected]>","sha":"a397bb72d52e865d0f44c6983bf01c85875251e8"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195806","number":195806,"mergeCommit":{"message":"[Security
Solution] Update footer link in rule preview to go to rule details page
(#195806)\n\n## Summary\r\n\r\nCurrently, the rule preview footer will
open the rule flyout. Although\r\nthis behavior is consistent with other
previews (host, user, alert\r\netc.), the rule flyout does not provide
additional information for\r\nusers. This PR updates the footer go to
rule details page
instead.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/6de03775-b1a4-41b9-b233-7817d6cca8ec\r\n\r\n\r\n###
Checklist\r\n\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\r\n\r\n---------\r\n\r\nCo-authored-by: Jan Monschke
<[email protected]>","sha":"a397bb72d52e865d0f44c6983bf01c85875251e8"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: christineweng <[email protected]>
@christineweng christineweng added backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) and removed backport:prev-major Backport to (8.x, 8.17, 8.16) the previous major branch and other branches in development labels Oct 10, 2024
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.x

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

@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
8.x Cherrypick failed because the selected commit (a397bb7) is empty. It looks like the commit was already backported in #195833

Manual backport

To create the backport manually run:

node scripts/backport --pr 195806

Questions ?

Please refer to the Backport tool documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) release_note:skip Skip the PR/issue when compiling release notes Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team v8.16.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants