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] Indicator Match Field dropdown is slightly moved to the left when creating an Indicator match rule #182858

Open
vgomez-el opened this issue May 7, 2024 · 3 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:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.15.0

Comments

@vgomez-el
Copy link

Describe the bug:
When creating a new Indicator Match rule "Field" dropdown is moved to the left, and gets slightly out of the visible area as well as its content after selecting the "Indicator index field" field.

Kibana/Elasticsearch Stack version:

8.14 BC3

Browser and Browser OS versions:

Google Chrome Version 123.0.6312.107

Original install method (e.g. download page, yum, from source, etc.):

Cloud deployment

Functional Area (e.g. Endpoint management, timelines, resolver, etc.):

Indicator Match Rule Creation

Steps to reproduce:

  1. Create a new Indicator Match Rule
  2. Fill Index patterns, custom query and indicator index patterns with values
  3. Start typing a field and select it from the dropdown
  4. Start typing an Indicator index field and select it from the dropdown

Current behavior:
After selecting the "Indicator index field", Field dropdown is moved to the left, and gets slightly out of the visible area as well as its content

Expected behavior:
All components should be clearly visible and inside the visible area.

Screenshots (if relevant):
image

REC-20240507140900.mp4
@vgomez-el vgomez-el added bug Fixes for quality problems that affect the customer experience triage_needed 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. Team:Detection Engine Security Solution Detection Engine Area labels May 7, 2024
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-engine (Team:Detection Engine)

@yctercero yctercero removed their assignment Jun 5, 2024
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:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.15.0
Projects
None yet
Development

No branches or pull requests

3 participants