We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 / Feature Request
Alerts that have either been Imported to a new Case or Merged into an existing Case cannot be deleted.
A
B
Deleted Cases should do a (optional?) cascading delete on relevant Alerts, assuming 1 Alert can only be imported to 1 Case.
^ Note that the selected alert cannot be Deleted, and that the Alerts count at the top has been marked as 0
Clicking on the link to the Alert produces the following error message:
Marking the alert as Unread yields the following:
The text was updated successfully, but these errors were encountered:
Same problem when I transform an alert to a case :
Alert stays in but I can't delete it.
[EDIT] Bug is known, see issue #1123 but no current patch
Sorry, something went wrong.
Hello , I have the same problem ..
rriclet
To-om
Successfully merging a pull request may close this issue.
Imported Alerts Cannot be Deleted
Request Type
Bug / Feature Request
Problem Description
Alerts that have either been Imported to a new Case or Merged into an existing Case cannot be deleted.
Steps to Reproduce
A
andB
A
to a CaseB
to CaseA
A
A
andB
will be there, marked as Imported and impossible to deletePossible Solutions
Deleted Cases should do a (optional?) cascading delete on relevant Alerts, assuming 1 Alert can only be imported to 1 Case.
Complementary information
^ Note that the selected alert cannot be Deleted, and that the Alerts count at the top has been marked as 0
Clicking on the link to the Alert produces the following error message:
Marking the alert as Unread yields the following:
Changes:
Disclaimer, these screenshots were staged to redact PII
The text was updated successfully, but these errors were encountered: