Change Task Status
Move a task through its status lifecycle without losing the activity trail that explains what changed and why.
Use the task patch route when the status transition should come from an integration or automation.
- Choose a valid status.
- Apply the transition from the correct surface.
- Preserve a clean activity trail.
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 a bearer token with `tasks.write`.
- 2. Pass the task id in the route path.
- 3. Send a JSON body containing only the new `status` when that is the only change.
- 4. Read the success response and then reload the task collection or detail page if you need the latest server state.
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.
Update Task Details
Change ownership, deadlines, labels, project links, description, or other mutable task fields without conflating that work with a status transition.
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.