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][ Alert List]User focus auto moved to Filter in for Timestamp column value expand cell content #121374

Closed
ghost opened this issue Dec 16, 2021 · 5 comments
Closed

[Security Solution][ Alert List]User focus auto moved to Filter in for Timestamp column value expand cell content #121374

ghost opened this issue Dec 16, 2021 · 5 comments
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. 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

Comments

@ghost
Copy link

ghost commented Dec 16, 2021

Describe the bug
User focus auto moved to Filter in for Timestamp column value expand cell content

Build Details

Version: 8.0.0-SNAPSHOT
commit:474d83d2bbc5dbe28ac4b4d2e9ddcecd434671fa
Build:48754

Pre-Conditions

  • Few Alerts should be generated on Kibana

Steps

  • Login to Kibana
  • Navigate to Alert Page
  • Click on expand cell content for any timestamp column value

image

  • click on expand cell content for any other column value let say hostname or Rule name
  • Observed that for timestamp column expand cell content modal user focus has been moved to filter in as filter in got highlighed in blue

image

Expected Result

  • User focus should not moved to any option available in expand cell content modal

image

Screen-cast

user-focus.mp4
@ghost ghost added bug Fixes for quality problems that affect the customer experience triage_needed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Dec 16, 2021
@elasticmachine
Copy link
Contributor

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

@ghost ghost added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Threat Hunting:Explore labels Dec 16, 2021
@manishgupta-qasource
Copy link

Reviewed & assigned to @MadameSheema

@michaelolo24 michaelolo24 removed their assignment Dec 17, 2021
@MadameSheema MadameSheema added Team:Threat Hunting:Investigations Security Solution Investigations Team and removed triage_needed labels Jan 10, 2022
@MindyRS MindyRS added the Team:Threat Hunting Security Solution Threat Hunting Team label Feb 23, 2022
@elasticmachine
Copy link
Contributor

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

@michaelolo24
Copy link
Contributor

@karanbirsingh-qasource - Closing, as this bug has been resolved via the refactoring work done here #144943 (comment)

@ghost
Copy link
Author

ghost commented Mar 22, 2023

Thanks @michaelolo24 for checking out the issue.

Issue is fixed on 8.7.0 BC6 ✔️ so adding QA:Validated label to the ticket.

Alerts.-.Kibana.Mozilla.Firefox.2023-03-22.11-09-01.mp4

@ghost ghost added the QA:Validated Issue has been validated by QA label Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. 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
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@MindyRS @elasticmachine @michaelolo24 @MadameSheema @manishgupta-qasource