Update Task Details
Change ownership, deadlines, labels, project links, description, or other mutable task fields without conflating that work with a status transition.
Use the task patch route to change mutable fields beyond status.
- Choose the correct mutation surface.
- Use null-clears or clear actions correctly.
- Keep the patch focused on the fields that truly changed.
Where this happens
Same Task, Other Interfaces
Use the version that matches where you are working now. The subject matter stays the same; the delivery changes by surface.
Do the work
- 1. Send only the fields that should change in the JSON body.
- 2. Use `null` for clearable fields such as `description`, `projectId`, `milestoneId`, `assigneeId`, or `deadlineAt` when the value should be removed.
- 3. If tags are included, send the full desired tag list rather than a partial append.
- 4. Keep status changes separate when you want the transition history to stay easy to read.
Keep Going in Task Workflows
Stay in the same interface and move to the next closest task in this topic when needed.
Browse Tasks
Open the main task surface, narrow the visible list, and move from the collection view into the next task action.
Create a Task
Create a task with the right title, ownership, and optional planning context from the start.
Change Task Status
Move a task through its status lifecycle without losing the activity trail that explains what changed and why.
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.