Help Center

Docs

Dependencies, Subtasks & Recurring Tasks

Model blocking relationships, break down work, and automate repeats

Subtasks

Break a task into smaller, trackable steps.

Open any task's detail panel and expand the Subtaskssection to add a checklist of smaller items. Subtasks share the parent's assignee and due date by default but can be individually reassigned or scheduled. The parent card shows a progress bar (e.g., 3 / 7) once subtasks exist.

  • Check off subtasks inline on the parent card, in the detail panel, or via the right-click menu.
  • Completing every subtask does not auto-complete the parent — you choose when the parent is done.
  • Subtasks are scoped to the parent and do not appear as top-level rows on the board.

Dependencies

Mark a task as blocked by or blocking another.

1

Open the task detail panel

Click the task whose dependency you want to set.

2

Expand the Dependencies section

You'll see two lists: Blocked by (prerequisite tasks) and Blocking (tasks that wait on this one).

3

Link a task

Use the search-and-add input to attach any other task. You can link across projects.

4

Read the blocked indicator

If any "blocked by" task is still open, this task shows a lock icon on the card. The icon clears once all prerequisites are Done.

Cycles are blocked
The CRM refuses to create a dependency that would form a cycle (A blocks B blocks A). You'll see a validation error when attempting the link.

Recurring Tasks

Automate tasks that repeat on a schedule.

Turn on the Recurring toggle on any task to open the recurrence editor:

  • Frequency — Daily, weekly, monthly, yearly, or custom (every N days / weeks / months).
  • Day selection — For weekly: pick one or more weekdays. For monthly: pick a day number or "last" / "first Monday" patterns.
  • End condition — Never, on a specific date, or after N occurrences.
  • Generation behavior — When the current instance is completed (or its due date passes), the next instance is created automatically with the same template fields.

Each generated instance is its own task record, so you can edit individual occurrences without disturbing the series. Edit the series master to change every future instance.

Pair with templates
The most durable pattern is a task template + a recurring schedule: template defines what to do, recurrence defines when.