Tasks are deliberately simple at the core and detailed where you need it.
Creating
Create from anywhere with the create palette, from a board column, or by asking Cortex. A task needs only a title; everything else is optional and can be added later.
The fields that matter
- ›Status drives the board. Keep the set small; five states cover almost every team.
- ›Priority (low, medium, high, urgent) is for triage, not for decoration. If everything is urgent, the field has stopped working.
- ›Assignee is one person. Shared ownership is how tasks stall; use subtasks for genuinely parallel work.
- ›Due date should mean something. Dates nobody honors train the team to ignore overdue signals.
Structure when you need it
Subtasks break work down; a parent shows progress across its children. Checklists are lighter than subtasks for steps that need no assignee or date. Dependencies mark that one task blocks another, which is what makes timeline views and slippage detection useful.
Time tracking
Optional per organization. When enabled, time entries roll up to the task, the project, and reports. Agencies and anyone billing by the hour should turn it on; product teams usually should not.
Tip: Ask Cortex to decompose a big task rather than writing subtasks by hand. It reads the description and proposes a breakdown you can edit before it is created.