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] Inconsistent Tag Selection Behavior in Alerts Table and Details Flyout #203173

Open
pborgonovi opened this issue Dec 5, 2024 · 3 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Alert Details Page Observability ux management team 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.

Comments

@pborgonovi
Copy link
Contributor

Description:

Tags applied to alerts are inconsistently displayed as selected between the Alerts Table and the Details Flyout. When applying tags via the More Actions menu in the Alerts Table, previously applied tags are correctly marked with a check. However, when applying tags via the Take Action menu in the Details Flyout, previously applied tags are not marked with a check on subsequent interactions.

Kibana/Elasticsearch Stack version:

8.18 Snapshot

Functional Area:

Alerts Management

Pre requisites:

  1. Rules are available
  2. Alerts have been generated by the rules

Steps to reproduce:

  1. Navigate to the Alerts Table.
  2. Select an alert and click More Actions > Apply alert tags.
  3. Apply a tag to the alert.
  4. Repeat Step 2 and observe that the previously applied tag is correctly marked with a check.
  5. Expand the same alert to open the Details Flyout.
  6. Click the Take Action button and select Apply alert tags.
  7. Add a new tag.
  8. Repeat Step 6 and observe the tag selection state.

Current behavior:

  • When applying tags via the Alerts Table, previously applied tags are marked with a check as expected.
  • When applying tags via the Details Flyout, previously applied tags are not marked with a check, creating inconsistency in the user experience.

Expected behavior:

  • Previously applied tags should be consistently displayed with a check, regardless of whether tags are applied via the Alerts Table or the Details Flyout.

Evidences:

Screen.Recording.2024-12-05.at.11.05.12.AM.mov
@pborgonovi pborgonovi added bug Fixes for quality problems that affect the customer experience Feature:Alert Details Page Observability ux management team 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. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team triage_needed labels Dec 5, 2024
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@yctercero yctercero added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed triage_needed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Jan 3, 2025
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 Feature:Alert Details Page Observability ux management team 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.
Projects
None yet
Development

No branches or pull requests

3 participants