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] Same Dot Colors Used for Medium and High Severity in Rule Creation #207021

Closed
sukhwindersingh-qasource opened this issue Jan 17, 2025 · 5 comments
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. Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v9.0.0

Comments

@sukhwindersingh-qasource

Describe the bug:

  • Same Dot Colors Used for Medium and High Severity in Rule Creation

Build Details:

VERSION: 9.0.0
BUILD: 82760
COMMIT: ba92d08

Preconditions

  • Kibana should be running.

Steps to Reproduce

  • Navigate to the Deployment Rules>Detection rules (SIEM)>Create new rule
  • Fill in required details
  • Now Click on the Default severity dropdown
  • Observe that Same Dot Colors are Used for Medium and High Severity in Rule Creation

Actual result

  • Same Dot Colors Used for Medium and High Severity in Rule Creation

Expected Result

  • Dot Colors should be different for the different Severity in Rule Creation

What is working

  • It working correctly on the Alerts tab 9.0 ✔

Image

  • It working correctly on 8.18.0 snapshot rules creation ✔

Image

Screen-cast

Create.new.rule.-.Kibana.Mozilla.Firefox.2025-01-17.11-59-54.mp4

Image

Logs

  • N/A
@sukhwindersingh-qasource sukhwindersingh-qasource added 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. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v9.0.0 labels Jan 17, 2025
@elasticmachine
Copy link
Contributor

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

@sukhwindersingh-qasource
Copy link
Author

@muskangulati-qasource Please review this

@muskangulati-qasource
Copy link

Reviewed and assigned to @MadameSheema

@MadameSheema MadameSheema removed their assignment Jan 17, 2025
@MadameSheema MadameSheema added the Team:Detections and Resp Security Detection Response Team label Jan 17, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@banderror
Copy link
Contributor

Thanks @sukhwindersingh-qasource, this is being tracked in #204737 and will be fixed in #206276.

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. Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v9.0.0
Projects
None yet
Development

No branches or pull requests

5 participants