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] Showing click to filter by field when we hower on added metric to cases but it is not clickable. #145819

Open
sukhwindersingh-qasource opened this issue Nov 21, 2022 · 3 comments
Open

[Security Solution] Showing click to filter by field when we hower on added metric to cases but it is not clickable. #145819

sukhwindersingh-qasource opened this issue Nov 21, 2022 · 3 comments
Assignees
@cnasikas
Labels
bug Fixes for quality problems that affect the customer experience Feature:Cases Cases feature impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@sukhwindersingh-qasource
Copy link

Describe the bug:
Showing click to filter by field when we hower on added metric to cases but it is not clickable.

Build Details:

VERSION: 8.6.0
BUILD: 58392
COMMIT: 50a7feb0a5eb068d3acccc49c83b9ccb6db6734f

Preconditions

  1. Kibana should be running.
  2. Data should be present for all explore tabs.
  3. Created case should be present

Steps to Reproduce

  1. Navigate to Security
  2. Click on explore tab.
  3. Select hosts then click on metric more option.
  4. Select add to existing case and then view case.

Actual Result
Showing click to filter by field when we hower on added metric to cases but it is not clickable.

Expected Result
Should not Showing click to filter by field when we hower on added metric to cases.

Screen Shot

click
@sukhwindersingh-qasource sukhwindersingh-qasource 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: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Nov 21, 2022
@elasticmachine
Copy link
Contributor

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

@sukhwindersingh-qasource
Copy link
Author

@karanbirsingh-qasource Please review this issue.

@MadameSheema MadameSheema added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Cases Cases feature and removed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Nov 21, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cnasikas cnasikas

Labels
bug Fixes for quality problems that affect the customer experience Feature:Cases Cases feature impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@cnasikas @elasticmachine @MadameSheema @karanbirsingh-qasource @sukhwindersingh-qasource