Updates part of one task, following JSON Merge Patch. Send only the fields to change: a field left
out is not touched, so a quick action (moving the task on the calendar, a status button, a checklist
tick) never overwrites details it did not send, such as the description. A field sent as null is
cleared: description, statutory due date, time estimate, checklist, assignee, team, category, service
and primary client. The name, status, dates and times are required on a task, so sending one of those
as null is a 400.
Clients: the same rules as a full update. The primary client always stays on the task, and a task
with clients but no primary gets its first client as primary. To remove every client, send the client
list and the primary client as null. Changing the primary client clears the task's service and
pipeline links (they belong to a client) unless a service code is sent.
The change is saved through the same update as a full update, so dated workflow steps follow the
task when its dates move (unless MoveWorkflowStepDates is false), and colleagues see the change live.
Only a saved task can be patched. A projected (upcoming) task must be materialised first.
Parameters
| Name | Type | Description |
|---|---|---|
| tenant* | path string | The Tenant.Code |
The Tenant.Code |
||
| code* | path string | |
Request Body*
{
"name": "string",
"description": "string",
"status": "NotStarted",
"startDate": "2024-01-01",
"dueDate": "2024-01-01"
}