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]investigate in timeline for blank value have no response #121499

Closed
ghost opened this issue Dec 17, 2021 · 5 comments
Closed
Labels
bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium 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 17, 2021

Describe the bug
investigate in timeline for blank value have no response

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
  • Hover the mouse over the blank value
  • click on investigate in timeline
  • Observed that no response for investigate in timeline for blank value

Whats-working

  • investigate in timeline for blank value is working in timeline result

image

Screen-Cast

investigate.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. Team:Threat Hunting:Investigations Security Solution Investigations Team v8.0.0 labels Dec 17, 2021
@ghost ghost added the impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. label Dec 17, 2021
@manishgupta-qasource
Copy link

Reviewed & assigned to michaelolo24

@elasticmachine
Copy link
Contributor

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

@michaelolo24
Copy link
Contributor

Per our team meeting - Use common function for filter and add to timeline functionality. In this scenario default to using exists/not exists bool.

@logeekal
Copy link
Contributor

@michaelolo24 , @karanbirsingh-qasource , This bug was resolved as part of 8.4 here : #138510

@ghost
Copy link
Author

ghost commented Aug 30, 2022

Hi @logeekal

we have validated this issue on main branch and found the issue to be fixed now ✔️ .

Build Details:
Branch: Main

Screen-Cast:

ubuntu-20.04-desktop-kibana.-.VMware.Remote.Console.2022-08-30.14-15-34.mp4

Hence we are closing this bug and adding "QA:Validated" to it.

thanks!!

@ghost ghost closed this as completed Aug 30, 2022
@ghost ghost added the QA:Validated Issue has been validated by QA label Aug 30, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium 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
Development

No branches or pull requests

6 participants