You can use Subtasks to split tasks into smaller parts, or to define more detailed goals and assign them to multiple people.

Subtasks are full Tasks with their own assignees, dates, comments and files.

How to Create Subtask

To create a subtask:

  • Select your parent Task, to load it in the Inspector. 
  • In the Subtasks section of the inspector, click on [Add Subtask]. 
  • (On Cirkus web , click the (+) button, and on iOS, go to the Subtasks tab in Task details.)

  • In the New Subtask sheet fill out all the information as you would for a Task.

    The Subtask will be assigned to your own user by default, but you can assign it to any project Member, Role, or email address.

  • You can also select a template to apply to your Subtask if one is available in your Workspace.
    Add files, dates and priorities, as you would with any normal Task.

  • Click OK to create the task

Working with Subtasks

  • When a Task has a Subtasks you will see a Subtask count in the Task cell, along with an indicator of Subtask completion with a pie chart.
    There are two options on how the parent and subtask status are - dependant or independent 
  • You can also click into a Task and manage them via in the Subtasks tab.
  • Collaborators will be notified of Subtasks activity in their Inbox just like they are for tasks.
  • You can star Subtasks and they will be pinned to your Starred Tasks.
  • Subtasks have numbers which are relative to the Parent i.e Parent task 123, will have subtasks 123-1, 123-2 etc
  • You can include Subtasks in your advanced Search and csv exports.
  • You can add start and end dates to Subtasks and they will show in your Schedule.
  • You can define if the parent Task status is Independent or if it depends on Subtask Status in Tasks and Template options. Read more about this setting here.
  • You can decide how Subtasks are shown in your Tasks list, if at all, through the Showing/Filter menus.
    - Off: no subtasks are shown in the list
    - Nested: subtasks are always nested under their parent, regardless of the filter or sort applied.
    - Independent: Subtasks are sorted and filtered independently

Subtasks in Task Templates

A really powerful way to use Subtasks is with Task Templates.

You can create a Task Template with custom fields, statuses, workflows and now Subtasks.

To add Subtasks to your Task Templates.

  1. As Workspace Admin, go to your Workspace, and Templates tab, then “Task Templates”
  2. Select the Task template you want to edit, and click through to the “Subtasks” tab of that Template.
  3. There you can add the Subtasks that you want to include in the Template.
  4. You can also set conditions for the Subtask within the Template.
    For example, when creating a Request if the requestor sets “Captioning needed” = YES, Subtasks will be created for “Captioning” and “Captioning QC “.
    If “Captioning needed” = NO, on the parent Task, the Subtasks will not be created.|
  5. You can also set Dates on the subtask which are relative to the parent. 
    In the screenshot the subtask will be created with a due date 2 days before the Parent task is due.
    You can have any subtask standard date set relative to any date field on the parent i.e subtask due on parent start date.
    These dates are applied only on task creation.
    (There is a similar feature for Tasks and Subprojects in Project Templates)
  6. If you are using Subtasks in Task Templates you can specify if the Parent status should be “Depends on Subtasks” or “Independent”. This is set in Task Template>Info, and the option only appears when the Template already has subtasks.
    Note: when using “Depends on Subtasks” mode it is not possible to define the assignee of a Task Template as it will be implicitly set from the assignees of the Subtasks. 

Note: Subtasks in Task Templates is a Pro feature an can only be used in Pro Workspaces on For more information check

Parent and Subtask status Options

When you create subtasks under a parent tasks, by default the parent will have its own status too i.e if all subtasks are done, the parent will still be Not Done.

This is a useful feature if some work also needs to be completed on the parent task, for example QC, or final delivery.

On the other hand, if the subtasks are a list of things to do and when this list is completed the body of work is completed, then you should use the “Depends on Subtasks” Parent Status setting

Parent status “Independent” example

Parent can have it’s own Assignees and status, and must be completed seperately.

Changes in the parent do not affect the subtasks, and vice versa.

Parent status “Depend on Subtasks” example

Parent does not have own assignees or status. They depend on the completion (Done, Not Done) of the subtasks.

When all subtasks are done, the parent is done.

When parent task assignee status is updated, all subtasks are also updated

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.