Dependencies and subtasks

Under Linked work on the task detail, Add dependency and Add subtask connect tasks to each other.

Blocked by

The strong link. Task A blocked by task B means A cannot proceed until B is finished. The board shows a red Blocked (n) chip on the card, and the task detail lists each blocker with its current status — so you can see at a glance whether the thing in your way is nearly done or has not started.

Cycles are rejected: the app refuses a dependency that would make two tasks block each other, directly or through a chain.

Relates to

The weak link — two tasks that inform each other but neither blocks the other. Shown as a blue Relates (n) chip.

Subtasks

A parent-child link for splitting a large piece of work. The child is a full task in its own right: it has its own key, sits in its own column, and can be assigned to someone else.

Tip

A practical rule: use blocked by when the order genuinely matters, relates to when you only want the reader to know the other task exists, and subtasks when one deliverable needs several people or several days.