> ## Documentation Index > Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt > Use this file to discover all available pages before exploring further. # Tasks > Break tickets into tracked subtasks with assignees, completion checkboxes, nested subtasks, and reusable templates for common multi-step workflows. Break down complex tickets into actionable task items with descriptions, assignees, and completion tracking. Create reusable task templates to standardize common workflows and ensure consistency across your team. ## Mental model Tasks are checklist items within a ticket. They break down a ticket's work into discrete, trackable steps with optional assignees and completion status. Tasks are not separate tickets. They live inside a single ticket and share that ticket's context, channel, and permissions. Key distinction: tasks vs child tickets. | Feature | Tasks | Child tickets | | ------------------- | -------------------------------------- | ---------------------------------------------------- | | **Scope** | Checklist items within one ticket | Separate tickets with their own lifecycle | | **Depth** | Up to 3 levels of nesting | Unlimited parent-child hierarchy | | **Assignee** | Multiple assignees per task | One assignee per ticket | | **Status** | Complete/incomplete (checkbox) | Full status workflow (Open, In Progress, etc.) | | **Notifications** | Task assignees become ticket followers | Each child ticket has independent notification rules | | **Cross-workspace** | No, tasks exist within one ticket | Yes, parent and child can be in different workspaces | | **Templates** | Task templates for reusable checklists | No template system for child ticket structures | Use tasks for simple checklists where each item is a discrete action step. Use child tickets when each item needs its own status workflow, assignee lifecycle, or cross-team visibility. *** ## Task templates Task templates are workspace-scoped, reusable sets of task items. When imported into a ticket, the template's tasks are copied into the ticket. After import, the tasks are independent of the template. Key behaviors: * Importing a template **replaces** all existing tasks in the ticket. It does not merge or append. * Changes to a template do not affect previously imported tasks. * Templates support the same 3-level nesting as regular tasks. * Templates can have default assignees. When imported, those assignees are automatically added as followers on the ticket. * Templates can be organized into folders for easier management. Folders are purely organizational and do not affect template behavior. Common template patterns: * **Onboarding checklists**: Account provisioning, equipment setup, orientation scheduling. * **Incident response**: Acknowledge, assess, notify, investigate, fix, verify, post-mortem. * **Change management**: Request, review, approve, implement, verify, document. *** ## Tasks in automation Tasks can be created and managed through the Ravenna API and agent tools. The agent can: * List tasks assigned to the current user across the workspace, with linked ticket context. * Create tasks on a ticket with descriptions and assignees. * Import task templates into a ticket. * Mark tasks as complete. Workflow actions can also interact with tasks when building automated processes. *** ## Constraints and gotchas * Tasks nest up to 3 levels deep (parent, child, grandchild). Deeper nesting is not supported. * Deleting a parent task deletes all its subtasks. * Tasks cannot be reordered after creation. They display in creation order. * Importing a template replaces all existing tasks in the ticket. This is destructive and cannot be undone. * Task templates are workspace-scoped. There is no cross-workspace template sharing. * Assigning a user to a task automatically adds them as a follower on the parent ticket. This cannot be disabled. * Task completion does not trigger ticket status changes. Completing all tasks does not automatically close the ticket. * Tasks do not have their own due dates, priorities, or statuses beyond complete/incomplete.