Subtasks

Big assignments rarely have a single owner or a single step. Subtasks let you decompose a task into smaller, individually trackable items while keeping them anchored to the parent.

A subtask is just a task that points to another task as its parent — it has its own assignee, status, due date, comments, and attributes. Anything you can do to a top-level task, you can do to a subtask.

Creating subtasks

There are a few ways to nest a task under a parent.

By dragging one task onto another. In any list, drag a task and drop it on top of another to nest it as a subtask. This is usually the fastest way to reorganise an existing flat list into a hierarchy.

From the parent task’s detail panel. Open any task and scroll to the Subtasks section. The new-task row at the bottom of that section creates a child of the open task — no extra step needed to set the parent.

By grouping a list by Parent task. In any list, switch the grouping to Parent task. Each existing parent becomes a group; adding a task into a group automatically nests it under that parent.

By setting Parent task on any task. Open a task’s detail panel and use the Parent task field to point it at another task. This works whether the task already has a parent or not.

Reorganising the hierarchy

The hierarchy is just the Parent task field — change it and the task moves.

Re-parent: change Parent task to a different task.
Promote to top-level: clear the Parent task field. The task becomes a regular top-level task again.
Nest deeper: a subtask can itself have subtasks. There’s no enforced depth limit, though deeply nested trees get harder to scan visually.

Working with subtasks across views

Each task’s detail panel includes a Subtasks section that’s a fully filtered task table — same columns, sorting, filtering, and display options as any other list. The Open in full view button (top right of the section) takes you to the All tasks list pre-filtered to children of the current parent, useful when you want more screen real estate.

In any list, Parent task behaves like any other built-in attribute:

Filter by it to narrow a list to children of one or more parents.
Group by it to organise a flat list into parent-led sections.
Display it as a column to show each task’s parent inline.

Completion is independent

Each task — parent or child — completes on its own. Marking a parent as Done does not change the status of its subtasks, and finishing every subtask doesn’t auto-complete the parent. This is intentional: it lets a parent stay open as a tracking umbrella even after the most concrete work is checked off.

What happens on delete

Deleting a parent doesn’t delete its subtasks — they’re promoted to top-level and remain in the workspace. If you want to discard a whole subtree, delete the children first (or move them under a different parent beforehand if you want to preserve them).