-
Notifications
You must be signed in to change notification settings - Fork 242
FOUR-28600: API to delete cases and the related requests in Swagger #8675
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
base: develop
Are you sure you want to change the base?
Conversation
FOUR-28685: Create an API to delete Cases and related Requests
|
You have run out of free Bugbot PR reviews for this billing cycle. This will reset on January 21. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
|
QA server K8S was successfully deployed https://ci-5a04878444.engk8s.processmaker.net |
|
QA server K8S was successfully deployed https://ci-5a04878444.engk8s.processmaker.net |
Record deletion moved to trait to resolve sonarqube complexity issue (too many methods in DeleteCase)
|
QA server K8S was successfully deployed https://ci-5a04878444.engk8s.processmaker.net |
FOUR-28723 | Store Logs For Deleting Cases via API
FOUR-28794: Delete notifications tied to case on delete and add test
|
QA server K8S was successfully deployed https://ci-5a04878444.engk8s.processmaker.net |
|





Issue & Reproduction Steps
Admins need an API endpoint to delete Cases and their related Requests, as described in the product document. The absence of this endpoint forces manual cleanup and can leave inconsistent data.
Solution
How to Test
Related Tickets & Packages
ci:deploy
...
Code Review Checklist