Skip to Content
Tasks

Root Tasks and Subtasks Hierarchy

How to break a large task into smaller subtasks, when to use the parent–child structure, and tips on managing unbounded subtask depth.

Administrator · 02/05/2026 · 344 views

1. Parent–child structure

The module supports unbounded depth between tasks:

Project
 └── Root task
       ├── Subtask 1
       │   ├── Sub-subtask 1.1
       │   └── Sub-subtask 1.2
       ├── Subtask 2
       └── Subtask 3
  • A root task belongs directly to a project.
  • A subtask sits under another task and breaks it down.

2. When should you create subtasks?

Create a subtask when:

  • A task is estimated to take more than 3 days — split for visibility.
  • Multiple people are working on different chunks of one larger task.
  • You need different tags or deadlines on different chunks.

Avoid subtasks when:

  • The task can be finished in a few hours — no need to subdivide.
  • The steps are linear, can't run in parallel, and don't need their own checkpoints.

3. Two ways to create a subtask

3.1. Create from the parent task

  1. Open the parent task.
  2. Scroll to the Subtasks tab → Add subtask.
  3. Enter the name and save — the subtask inherits the project and several attributes from the parent.

3.2. Automatic breakdown

Some projects support automatic breakdown: the system uses the parent task description to suggest subtasks. Useful when scaling up a large piece of work.

4. Managing subtasks effectively

Situation Recommendation
Parent done while subtasks are still "In Progress" The system warns you — close the subtasks first or convert them into root tasks.
Subtasks too deep (more than 3 levels) Consider a sub-project — a sign the root task is too large.
Need total hours reporting Parent total = sum of subtask actual hours + hours logged directly on the parent.

5. Real-world examples

  • RAG feature development: Root "Implement RAG system" → subtasks: schema design, embedding service, retriever, UI integration, tests.
  • Customer rollout: Root "Go-live for Customer A" → subtasks: prepare environment, migrate data, user training, hypercare.
  • Marketing: Root "Launch new product" → subtasks: design landing page, write blog post, produce demo video, social posts.