-
Notifications
You must be signed in to change notification settings - Fork 639
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
[Bug] Issues surrounding Alerts merging #1557
Comments
#1553 Seems to be related to this? |
rriclet
added a commit
that referenced
this issue
Oct 23, 2020
rriclet
added a commit
that referenced
this issue
Oct 26, 2020
rriclet
added a commit
that referenced
this issue
Oct 27, 2020
To-om
pushed a commit
that referenced
this issue
Oct 27, 2020
To-om
pushed a commit
that referenced
this issue
Oct 27, 2020
To-om
pushed a commit
that referenced
this issue
Oct 27, 2020
Responding to your problem description :
|
Sweet thank you for fixing this!! I will re-evaluate #2 once we get 4.0.1. |
I reproduced 2. by importing an alert with a case template. I fixed this bug with issue #1552. |
To-om
pushed a commit
that referenced
this issue
Nov 13, 2020
To-om
pushed a commit
that referenced
this issue
Nov 13, 2020
To-om
pushed a commit
that referenced
this issue
Nov 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This Issue is intended to serve as a list of issues when merging multiple alerts into one case
Request Type
Bug
Work Environment
Problem Description
When merging multiple alerts into a single case, multiple issues occur.
Steps to Reproduce
Complementary information
Looking at the trace logs there are no errors generated. I am currently scrubbing out any PII or IP data that can't be shared, and I will follow up with this data. I have a log of merging about 10 alerts into a single case and it generated >12000 lines of data so this will take a bit to pair down.
The text was updated successfully, but these errors were encountered: