Details
-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Description
AT:
- in the report REST-API documentation the new behavior is documented as well
- when there are conflicts when updating/deleting the report, then I get a 409 response code and I can see the resources that are affected in the response
- I can enforce to update/delete a report event when there are conflicts using a query parameter - I then get a 204 on successful execution
- If there are no conflicts I get an 204 response code
- I can prefetch the conflicts of a delete operation using GET /api/reports/<id>/delete-conflicts
Possible conflicts are:
- delete but used by other item
- updating report type but used in other item and new type is not compatible
- used in alert
- supported types:
- Number
- supported types:
- used in combined report
- check if report is still combinable with it's siblings
- used in dashboard
- not affected
- used in alert