-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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][Case] Attach multiple alerts to case #91292
Labels
Feature:Cases
Cases feature
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
jonathan-buttner
added
Team:Threat Hunting
Security Solution Threat Hunting Team
Feature:Cases
Cases feature
labels
Feb 12, 2021
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
cnasikas
added
the
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
label
Feb 15, 2021
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-threat-hunting-cases (Team:Threat Hunting:Cases) |
cnasikas
added
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
and removed
Team:Threat Hunting
Security Solution Threat Hunting Team
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Team:Threat Hunting:Cases
labels
Jan 10, 2022
Pinging @elastic/response-ops (Team:ResponseOps) |
Implemented by #128875 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature:Cases
Cases feature
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Allow the user to bulk attach alerts to a case. Currently a user can only attach a single alert at a time to a case. The detection rules feature being worked on here: #88726 will allow detection rules to automatically attach generated alerts to cases but it'd probably still be helpful to allow a user to manually attach multiple alerts to a case.
The text was updated successfully, but these errors were encountered: