The modules
Task lists
Always on, in every project. Where the work itself lives.

- Lists. A project can have several. A list can use its own workflow, so a support queue and a build backlog do not have to share stages.
- Four views. List, board, table and graph — the same work, arranged differently. Switching is a display choice, not a move.
- An internal task. Marked internal, so a client never sees it.
Lists and stages
A project starts with one list. Add more when a project has genuinely different kinds of work — a build backlog and a support queue want different stages, and forcing them into one pipeline makes both worse.
Stages are the columns work moves through. They come from a workflow — a named set of stages your org keeps in Org settings › Workflows. A project uses one, and any list can pick its own in list settings. Edit a workflow once and every project using it follows.
Each stage has a category underneath it — to do, in progress, blocked, done, discarded — which sets the column order and is what the dashboard counts. Rename stages freely; the category is what carries meaning. Switching a list to another workflow shows where each stage goes before anything moves.
Tags belong to the project, not to a list: type a new one on any task. Org tags, set up in Org settings › Tags, are available in every project.
The four views
- List — everything in order, fastest to scan.
- Board — one column per stage, for moving work along.
- Table — every field at once, for bulk edits and sorting.
- Graph — how work blocks other work.
Searching a project
Press / anywhere in a project, or use the search box in its header, to search task titles, descriptions and comments along with the project's docs and meetings. Results come back in one list, ranked by relevance, and you can narrow them by type, open or closed, list and stage. The switch next to the box widens the search to every project you can open. In ⌘K, the last row, "See all results", opens the same page.
Subtasks, blockers and references
A task can have subtasks, and can be marked as blocked by another task. A blocked task shows what is blocking it on the dashboard — and a blocker that is already finished does not count, which is usually what you want.
Typing a task's key anywhere — a comment, a document, another task — turns into a link back to it, with a backlink at the other end.
Internal tasks. A task, or a whole list, can be marked internal so clients never see it. See internal vs client-visible.