Skip to content

[AI4SOC] [Bug] Alert is not attached to the case if the already attached alert is used #220469

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
Open
muskangulati-qasource opened this issue May 8, 2025 · 3 comments
Open

[AI4SOC] [Bug] Alert is not attached to the case if the already attached alert is used #220469

muskangulati-qasource opened this issue May 8, 2025 · 3 comments
Assignees
@peluja1012
Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Security Generative AI Security Generative AI Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed v9.1.0

Comments

@muskangulati-qasource
Copy link

Describe the bug
Alert is not attached to the case if the already attached alert is used

Kibana/Elasticsearch Stack version

VERSION: 9.1.0
BUILD: 86274
COMMIT: e55132a8c0ad47be02ed35120fd122540ba9d78d

Steps

  1. Kibana AI4DSOC SERVERLESS environment should exist
  2. Trigger the alerts
  3. Generate Attack Discovery for the alerts
  4. Add the discovery to the case
  5. Navigate to the newly created case
  6. Click on the expand (>) icon for the alert
  7. Click on take action for the alert in the flyout
  8. Click on add the alert to case
  9. Observe, the user gets a success message but the alert is not attached

Expected Result
The alert should be attached correctly as per the notification of successful attached alert

Screenshot

Alert.not.attached.to.case.mp4
@muskangulati-qasource muskangulati-qasource added bug Fixes for quality problems that affect the customer experience triage_needed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Security Generative AI Security Generative AI v9.1.0 labels May 8, 2025
@elasticmachine
Copy link
Contributor

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

@muskangulati-qasource
Copy link
Author

@arvindersingh-qasource please review!

@arvindersingh-qasource
Copy link

Reviewed and Assigned to @peluja1012

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

@peluja1012 peluja1012

Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Security Generative AI Security Generative AI Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed v9.1.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@peluja1012 @elasticmachine @muskangulati-qasource @arvindersingh-qasource