Tasks

The unit of work. Types, priorities, status, drag-drop, inline editing, filtering, subtasks, and deep linking by URL.

A task is one unit of work. Tasks are the only thing you actually ship, releases and areas are planning shells around them.

Anatomy of a task

Every task has:

  • Title, what the change is, in one line.
  • Description, markdown body for context, repro steps, or design notes.
  • Type, feature, bug, or improvement.
  • Priority, low, medium, high, or urgent.
  • Status, to-do, in-progress, or done.
  • Area (optional), which part of the system. See Areas.
  • Release (optional), which release it ships in. See Releases.
  • Assignee (optional), who owns the work. See Team & invites for setup.

When you create a new task, it auto-assigns to the project's active release.

The task board

The board view shows three columns by default: To Do / In Progress / Done. Drag-and-drop a card to change its status, the change syncs to every connected session in real time.

Each column is collapsible (click the header). The collapsed state persists across page loads.

The list view

Toggle to list view from the toolbar. List view groups tasks by status (or by release, depending on filter), and shows more metadata per row: type, priority, assignee, area. Useful for triage when you want to see lots of tasks at once.

Your view choice (board vs list) persists per project.

Filtering

The task page has filter tabs along the top:

  • All, every task in the project.
  • Features, only feature-type tasks.
  • Bugs, only bug-type tasks.
  • Active release, only tasks attached to the current active release.

Filters compose with the URL, share a filtered view by sharing the URL.

Inline editing

Hover any task card and click the title to edit it inline. Type, hit Enter, done. No modal, no round trip. Useful for renaming a batch of tasks quickly.

Deep linking

Every task has a stable URL: /u/<username>/<projectid>/tasks/<taskid>. Visiting that URL opens the project at the task modal. Share it in Slack, paste it in a PR description, or bookmark it, it always lands on the right task.

Subtasks

A task can have a checklist of subtasks inside the modal. Use them when one task has multiple obvious steps but doesn't justify spawning multiple full tasks with their own metadata, repro steps, acceptance criteria, "don't forget X" reminders.

Spawn a new task instead when the work has its own owner, priority, or could ship independently. If you want to assign a subtask to someone else, that's the signal, turn it into a task.

Adding and editing. Open any task. The Subtasks section sits below the description. Click Add subtask, type, hit Enter. Tick the checkbox when each one is done. Click any subtask text to edit inline. Drag the handle to reorder.

Progress. Task cards show a small 3/5 indicator when subtasks exist. All subtasks complete doesn't auto-mark the task done, shipping is still a deliberate action.

Storage. Subtasks live inside the task document, not as separate entities. No per-task subtask limit, and they don't count against your active-task limit. They don't appear in CSV exports as their own rows.

Limits per plan

The free tier limits you to 250 active tasks across all projects. Done tasks don't count. Basic+ removes the cap. See Plans and limits.

What's next

Last updated