atlas-mcp-server
by cyanheads
Verified
update_task
Update task properties and status.
Status Transitions:
- PENDING → IN_PROGRESS, BLOCKED, CANCELLED
- IN_PROGRESS → COMPLETED, CANCELLED, BLOCKED
- COMPLETED → No transitions allowed
- CANCELLED → PENDING (for retry)
- BLOCKED → PENDING, IN_PROGRESS
Automatic Behaviors:
- Auto-transition to BLOCKED if dependencies block
- Parent completion requires all children complete
- Cancelled parent cancels non-completed children
- Blocked siblings prevent task completion
- Failed siblings prevent task start
Validation Rules:
- Same constraints as create_task
- Dependencies checked before status changes
- Parent-child status rules enforced
- Metadata schema validated
- Notes length and count limits applied
Best Practices:
- Document status change reasoning
- Update progress indicators
- Track technical implementation details
- Record blockers and resolutions
- Maintain dependency accuracy
Example: { "path": "project/backend/auth", "updates": { "status": "IN_PROGRESS", "progressNotes": [ "Database schema updated", "JWT library integrated", "Basic token generation implemented" ], "metadata": { "reasoning": "Moving to IN_PROGRESS as database dependencies are completed and core JWT implementation has begun. Token refresh mechanism still pending.", "technical_notes": [ "Using jsonwebtoken library for JWT operations", "Token expiry set to 1 hour with refresh window" ] } } }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path of task to update | |
| updates | Yes | Changes to apply to the task. Field constraints: - title: Task name (max 200 chars) - description: Task details (max 2000 chars) - type: TASK/MILESTONE classification - status: Task state with validation rules - parentPath: Parent task path (max 1000 chars, 10 levels) - dependencies: Required tasks (max 50) - metadata: Task tracking fields: - priority: low/medium/high - tags: max 100 tags, each max 100 chars - reasoning: max 2000 chars - tools_used: max 100 entries - resources_accessed: max 100 entries - context_used: max 100 entries, each max 1000 chars - technical_requirements: implementation details - acceptance_criteria: validation points - status_tracking: timestamps, block reasons - version_control: version numbers, states - notes: Each category max 100 notes, each note max 1000 chars - planningNotes: Planning and preparation - progressNotes: Implementation progress - completionNotes: Completion details - troubleshootingNotes: Issue resolution Status changes trigger: - Automatic dependency validation - Status propagation to parent tasks - Dependent task blocking - Child task status updates - Validation of all constraints |