Apply a sparse field patch to up to 100 tasks in a single transaction

POST 
/api/tasks/bulk-update

Apply a sparse field patch to up to 100 tasks in a single transaction. The patch accepts any non-empty subset of status, assigneeId, dueDate, and priority — at least one field must be present, otherwise the request is rejected with 400. Fields left out are untouched on every selected task. All-or-nothing semantics: if any task in the batch fails validation or update, the whole batch rolls back. Status values are validated per task's project — a status name missing from any selected task's project rejects the batch.

Request

Responses

200

Successful response

400

Validation error. Triggers: empty patch, malformed or duplicate task ids, > 100 ids in the selection, or a status name that is not configured for one or more selected tasks’ projects (per-project status validation throws ValidationError, which withErrorHandler maps to 400).

401

Unauthorized — authentication credentials are missing or invalid

403

Forbidden — requires tasks.update.any permission

404

One or more task IDs not found or not visible to the caller