Sub-Tasks

Sub-tasks help you break down complex tasks into smaller, manageable checklist items. Track progress on each step and see completion percentage at a glance.

What are Sub-Tasks?

Sub-tasks are lightweight checklist items within a parent task. Unlike full tasks, sub-tasks:

  • Don't have their own status, priority, or assignees
  • Can be checked off as completed
  • Show progress as a percentage bar
  • Help break down work without cluttering the board
Sub-Tasks Example

Creating Sub-Tasks

  1. 1.Open any task by clicking on it
  2. 2.Scroll to the Sub-Tasks section
  3. 3.Click + Add button
  4. 4.Type the sub-task title and press Enter
  5. 5.Continue adding more sub-tasks as needed
Tip: You can add multiple sub-tasks quickly by pressing Enter after each one.

Managing Sub-Tasks

Completing Sub-Tasks

Click the checkbox next to any sub-task to mark it as complete. The progress bar updates automatically.

ActionResult
Click checkboxToggle completion status
Progress barShows % of completed sub-tasks

Editing Sub-Tasks

Click on any sub-task text to edit it inline. Press Enter to save or Escape to cancel.

Deleting Sub-Tasks

Hover over a sub-task and click the trash icon to delete it. A confirmation dialog will appear.

Progress Tracking

The sub-task section shows a visual progress indicator:

  • Fraction: Shows completed/total (e.g., "3/5")
  • Progress bar: Green bar fills as sub-tasks are completed
  • Percentage: Shows completion rate (e.g., "60%")

Best Practices

When to Use Sub-Tasks

Good uses:

  • Breaking down a feature into implementation steps
  • Creating a checklist for deployment procedures
  • Listing acceptance criteria for a user story
  • Tracking multiple deliverables within one task

Not ideal for:

  • Work that needs its own assignee (use separate tasks)
  • Items that need their own due dates (use tasks with dependencies)
  • Complex work with multiple statuses (use linked tasks)

Tips for Effective Sub-Tasks

  1. 1.Keep them small — Each sub-task should be completable in one session
  2. 2.Be specific — "Write unit tests for login" is better than "Testing"
  3. 3.Order logically — Put sub-tasks in the order they should be completed
  4. 4.Don't overdo it — If you have 20+ sub-tasks, consider breaking into multiple tasks

Keyboard Shortcuts

ShortcutAction
EnterSave new/edited sub-task
EscapeCancel editing

Related Features