Tasks
Status workflow, priorities, categories, automatic time tracking, assignment, the Kanban board, and the inline-editable Table view.
A task is the unit of execution inside a project. It optionally belongs to one milestone.
Status workflow
Tasks move through a Kanban flow:
Not Started ──▶ In Progress ──▶ Completed
│
└────────▶ BlockedThe four statuses are Not Started, In Progress, Completed, Blocked. Changing status on the board drives time tracking, milestone progress, and analytics automatically. When a task is set to Completed, its completion timestamp is recorded; moving it out of Completed clears it.
Priority and category
- Priority —
Low,Medium,High. Used across analytics and filtering. - Category — the kind of work. The product's task categories include Development, Design, Testing, Documentation, Strategy, Marketing, Finance, Research, Infrastructure, Compliance, Operations, and Analytics. (The MCP API accepts a category enum — see the MCP page for the exact list it validates.)
Estimates vs. actuals
Each task has estimated hours and actual hours. Estimates come from AI generation (or you set them); actuals reflect real effort and feed the "time progress" metric in Analytics.
Automatic time tracking
Time tracking is automatic — there is no start/stop button to remember:
- When a task enters In Progress, a timer starts (
in_progress_started_at). - When it leaves In Progress, the elapsed time is added to an accumulating total (
in_progress_total_seconds). - Re-entering In Progress resumes accrual on top of the existing total.
This means a task's tracked time is the sum of every interval it spent In Progress, with the currently-running interval included live while it's active.
Because tracking is driven by status, the most accurate time data comes from moving tasks to In Progress when you actually start, and out of it when you stop or finish.
Assignment
Tasks carry an assigned_to list, so a task can have one or more assignees (team members). Assignment changes are recorded in the Activity feed as an assigned action.
Due dates and milestones
A task can have a due date and can be grouped under a milestone (milestone_id). Grouping a task under a milestone contributes to that milestone's automatically-calculated progress. Unassigning (milestone_id cleared) removes it from that roll-up.
Comments
Each task has a discussion thread with one level of replies, auto-linked URLs, and @-mentions that notify teammates. See Comments.
The board across screen sizes
The Kanban board adapts: a swipeable single column on mobile, a scrollable two-column layout on tablets, and a four-column grid on desktop.
Table view
If you prefer a spreadsheet, the Table tab shows the current project's tasks as a dense, scannable grid — one row per task, one column per field. Every cell is editable in place:
- Click a cell to edit. Text (task name) and number (estimated hours) cells turn into inputs —
Enteror click-away saves,Esccancels. Status, priority, category, milestone, and assignees open a dropdown; due date opens a date picker. Edits save instantly and roll back with a toast if the save fails. - Comprehensive filtering. Search by text plus multi-select filters for status, priority, category, assignee, and milestone, and a due-date quick filter (overdue / today / this week). Active filters show as removable chips; Clear resets them.
- Sort and arrange. Click any column header to sort ascending → descending → off. Use Columns to show or hide fields — your choice is remembered on this device.
- Bulk edits. Turn on Select, tick rows, and change status or priority or delete in bulk from the action bar.
- Add a task from the row at the bottom of the sheet, or open the full editor from any row with the expand icon.
On mobile the sheet scrolls sideways with the task-name column frozen, so you never lose track of which row you're editing. Reach it from More → Table.
Related
- Comments — discuss a task in threaded comments.
- Milestones — how task status rolls up into progress.
- MCP integration — create/update/search tasks programmatically.