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.

Sign up for GitHub

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

Jump to bottom

[Security Solution] User information overlaps with alerts details flyout #128235

Closed
MadameSheema opened this issue Mar 22, 2022 · 4 comments
Closed

[Security Solution] User information overlaps with alerts details flyout #128235

MadameSheema opened this issue Mar 22, 2022 · 4 comments
Labels
enhancement New value added to drive a business result fixed QA:Validated Issue has been validated by QA Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team v8.6.0

Comments

@MadameSheema
Copy link
Member

Describe the bug:

  • User information overlaps with alerts details flyout

Kibana/Elasticsearch Stack version:

Steps to reproduce:

  1. Generate an alert with user.name information and open de details of it

Current behavior:

Screenshot 2022-03-22 at 09 59 13

Expected behavior:

  • The user name modal should not be overlapping with the alerts details flyout.
@MadameSheema MadameSheema added bug Fixes for quality problems that affect the customer experience triage_needed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Threat Hunting Security Solution Threat Hunting Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team labels Mar 22, 2022
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@michaelolo24
Copy link
Contributor

@MadameSheema this is not really a bug as it's more of a question of which flyout/popover should take precedence on the screen. @monina-n can help answer this, but I think since users can close either of the popovers really easily, it's really not a bug. I would consider this a discussion for a potential future enhancement

@michaelolo24 michaelolo24 added enhancement New value added to drive a business result and removed bug Fixes for quality problems that affect the customer experience triage_needed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Apr 12, 2022
@michaelolo24 michaelolo24 removed their assignment Apr 12, 2022
@michaelolo24 michaelolo24 mentioned this issue Apr 12, 2022
Closed
@christineweng christineweng mentioned this issue Nov 10, 2022
Merged
christineweng added a commit that referenced this issue Nov 16, 2022
@christineweng
[Security Solution][Bug] fix popover in t-grid (#145025)
05d1ff8 
This PR contains fixes for the following issues:

#### # 1 Popover overlaps flyout
- #139280
- #128235
#### # 2 Popover persists after clicking filter out
- #115341
#### # 3 Popover persists after clicking a button outside of popover
- #118844

## Background
Previously, a cell's popover remains open after clicking an action. In
many cases we want the popover to close upon clicking on a cell action.
EUI team addressed this by adding a `closeCellPopover` to a `ref` API.
- elastic/eui#5590

In T-grid, there are 2 types of cell actions: 
- Default cell actions such as filter in, filter out, add to timeline
and copy. `closeCellPopover` is not used.
- Formatted fields that have more information in the form of flyouts
(host name, user name, ip, etc.)
`closeCellPopover` prop is passed but currently not working as expected.

This PR contains fixes for: 
- Fixing `closeCellPopover` in T-grid body for formatted fields - fixes
# 1
- Adding `closeCellPopover` props in default cell actions - fixes # 2
and # 3

## # 1 - `closeCellPopover` in T-grid 

`dataGridRef.current?.closeCellPopover` was added and intended to close
any open popovers when a cell action is clicked. However, because it is
a mutable object, it is not being monitored in `columnsWithCellActions`.
When the page is initially loaded, `dataGridRef.current` remain as null
and it does not update until the page re-renders and `dataGridRef`
becomes non-null.
- After: popover closes properly


https://user-images.githubusercontent.com/18648970/201202326-ec657f78-c425-46a6-9356-f6e9ef1ab798.mov


## # 2 & # 3 Add `closeCellPopover` to default cell actions

- After: upon opening the expansion popover, clicking any options and
the popover will disappear


https://user-images.githubusercontent.com/18648970/201417542-063c514b-5474-4676-a747-a9401627c5e8.mov

- After: upon opening the expansion popover, clicking any options
outside and the popover will disappear


https://user-images.githubusercontent.com/18648970/201417678-7cf0fefa-f4a7-4a70-9a10-76b248323639.mov

Note for UX: although QA only flagged `filter out` and `add to
timeline`, for consistency's sake, the expansion popover will disappear
after clicking any of the cell actions, which includes `filter in` and
`copy`.
@ghost
Copy link

ghost commented Nov 17, 2022

Hi @MadameSheema
We have validated this issue on the latest 8.6.0-BC1 build and observed that the issue is fixed. Please find below the testing details:

Build Details:
VERSION: 8.6.0-BC1
BUILD: 58392
COMMIT: 50a7feb

Screen-Recording:

samrat.-.ec2-54-242-190-185.compute-1.amazonaws.com.-.Remote.Desktop.Connection.2022-11-17.14-30-25.mp4

Hence, we are closing this issue and marking it as QA Validated.

Thanks!

@ghost ghost closed this as completed Nov 17, 2022
@ghost ghost added the QA:Validated Issue has been validated by QA label Nov 17, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New value added to drive a business result fixed QA:Validated Issue has been validated by QA Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team v8.6.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@elasticmachine @michaelolo24 @MadameSheema @christineweng