Every time we add a new field to a case we need to update the Bulk Update Cases API to support the new fields. The API usually iterates over all requested cases to do field validations, data transformations, and data creation. This process can slowly make the API complex, difficult to maintain, and slow. We need to create a PATCH /api/cases/<case_id> endpoint dedicated to update a single case and support existing and new features. The Bulk Update Cases API should support a few selective operations like bulk deleting cases or bulk updating simple fields like the tags or the severity of a case.
Every time we add a new field to a case we need to update the Bulk Update Cases API to support the new fields. The API usually iterates over all requested cases to do field validations, data transformations, and data creation. This process can slowly make the API complex, difficult to maintain, and slow. We need to create a
PATCH /api/cases/<case_id>
endpoint dedicated to update a single case and support existing and new features. The Bulk Update Cases API should support a few selective operations like bulk deleting cases or bulk updating simple fields like the tags or the severity of a case.