-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Cases] Disable Case Connector #95469
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
QA:Needs Validation
Issue needs to be validated by QA
labels
Mar 25, 2021
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
Pinging @elastic/security-threat-hunting-cases (Team:Threat Hunting:Cases) |
Closing this as it is already completed |
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
QA:Needs Validation
Issue needs to be validated by QA
Team:Threat Hunting:Cases
labels
Jan 10, 2022
Pinging @elastic/response-ops (Team:ResponseOps) |
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)
The case connector feature is not yet complete. The remaining work is described here: #94115
Since the connector feature isn't yet complete it was disabled in this PR: #95122
Testing needs to be performed to validate that the existing case functionality has not been impacted by disabling the case connector. All case functionality should be tested:
The text was updated successfully, but these errors were encountered: