Tasks

A Task is a single piece of work that can be done by one person in one sitting, roughly. It has a title, a status, a priority, optional assignees, and up to three date fields (see Task timing).

Tasks never live on their own. They belong to either a project (initiative, workstream, or cycle) or another task as a subtask. The parent is how tasks roll up into higher-level views.

• Title — what needs to happen
• Status — todo / in_progress / done / cancelled
• Priority — urgent / high / medium / low / none
• Assignees — who owns it (0..N people)
• targetDate — external deadline
• startDate — when work begins (auto-derived from status if unset)
• endDate — when work is expected to finish (auto-derived from status if unset)
• parentTaskId — the task this is a subtask of, if any
• projectId — the initiative or workstream this belongs to
• cycleId — the sprint this is scheduled into
• tags — free-form labels

Three common entry points:

• On a Tasks page — click + Newabove the table or board
• Inside a project — every project page has an inline task list. Adding there sets projectId automatically
• From a doc — highlight one or more lines and pick → Task from the selection menu. Each line becomes its own task and the source text is linked to the new record

Click a task row to open it as a full page. The header shows pinned fields as inline-editable chips (status, priority, assignee, targetDate by default). Everything else lives in the Properties popover. See Customization for how to choose what's pinned.