-
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
[Cases] Allow users to push to external service when the case is closed #192552
Labels
appex-ro-mx-team-member-onboarding
enhancement
New value added to drive a business result
Feature:Cases
Cases feature
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
cnasikas
added
enhancement
New value added to drive a business result
Feature:Cases
Cases feature
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
labels
Sep 11, 2024
Pinging @elastic/response-ops-cases (Feature:Cases) |
Pinging @elastic/response-ops (Team:ResponseOps) |
heespi
added
appex-ro-mx-team-member-onboarding
and removed
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
labels
Sep 20, 2024
cnasikas
added
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
and removed
needs-team
Issues missing a team label
labels
Sep 21, 2024
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this issue
Nov 8, 2024
…case is closed (elastic#198146) Closes elastic#192552 ## Summary - Removed the restriction that didn't allow user to push a closed case to an external service. https://github.com/user-attachments/assets/82c49524-5685-40c0-b025-d6b38ab4e056 --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Antonio <[email protected]> (cherry picked from commit cc6ffef)
mbondyra
pushed a commit
to mbondyra/kibana
that referenced
this issue
Nov 8, 2024
…case is closed (elastic#198146) Closes elastic#192552 ## Summary - Removed the restriction that didn't allow user to push a closed case to an external service. https://github.com/user-attachments/assets/82c49524-5685-40c0-b025-d6b38ab4e056 --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Antonio <[email protected]>
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this issue
Nov 8, 2024
…case is closed (elastic#198146) Closes elastic#192552 ## Summary - Removed the restriction that didn't allow user to push a closed case to an external service. https://github.com/user-attachments/assets/82c49524-5685-40c0-b025-d6b38ab4e056 --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Antonio <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
appex-ro-mx-team-member-onboarding
enhancement
New value added to drive a business result
Feature:Cases
Cases feature
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Users can push cases to external services. If the case is closed it is not possible to push the case to the external service. This can lead to open cases in the external service and closed cases in Kibana. We should allow users to be able to push a closed case to an external service so they can be able to push the closed status to the external service.
The text was updated successfully, but these errors were encountered: