-
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
[Security Solution][Detections] Fixes show alerts for execution action on Rule Execution Log #128843
Conversation
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM,
- Verified the bug in my local env.
- Changed the code locally to match this
- Verified the fix
- Left a comment about no constancy (I didn't see an animation to let me know a filter is being added)
- Noticed it adds multiple filters but I think this is the intent of the UI/UX
- Ate an orange 🟠 along the way as I was slightly hungry.
@@ -223,7 +223,7 @@ const ExecutionLogTableComponent: React.FC<ExecutionLogTableProps> = ({ | |||
icon: 'filter', | |||
type: 'icon', | |||
onClick: (value: object) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should type this eventually other than object and remove the ugly get
below as that is just going to break later down the road.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that's no bueno -- will try to type
out the columns and then this can get cleaned up 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already had a type for this! 🙂 Addressed here: https://github.com/elastic/kibana/pull/129003/files#diff-81a89a66909bd6b3a6836daa93e7cef8100675de09e94244319ee60426a4c361R230-R232
Yeah we don't do that anymore. That's a relic of the drag and drop days my friend 😅 |
Thanks for the response and update on this PR. I would say the more appropriate statement I should make is, I was expecting a form of positive UI/UX feedback that something was added to the filter bar. This could have been one of the following or maybe something else:
I honestly missed the filter had been added on the click. |
You're welcome @FrankHassanabad! Thanks for the feedback! 🙂 I agree, it's definitely easy to miss and hard to tell that a filter has been added. I'm using the core provided global KQL |
💚 Build SucceededMetrics [docs]Async chunks
Unknown metric groupsESLint disabled in files
ESLint disabled line counts
References to deprecated APIs
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @spong |
Yeah, I don't know if that goes to them or UI/UX, but I think something to indicate that we indeed add a filter would be helpful. |
I can update the tooltip on the action as an immediate fix so the user at least has the potential to be aware of what's about to happen. Will also clear out all other filters when the action fires to prevent duplicate filters, although that has the undesired side effect of wiping any specific user filters, and there's no easy way for the user to undo. We discussed this in relation to the datepicker, which has |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
@FrankHassanabad, I have implemented the above changes and this action will now show a toast informing the user that their global query state has been updated, and the toast also includes a button to revert to their previous query so as to not interrupt their workflow. I've also created this enhancement request (#129542) to add support for a Thanks again for the UX feedback here, really appreciate it! |
Summary
One-liner fix for the
Show alerts for execution
action on the Rule Execution Log table. Had the wrong key after changing the response interface. Working on the follow-up feedback PR from #126215, and will be including additional test coverage there, but wanted to get this in before the first BC for testing purposes.