Subtasks help when one task becomes too large to control. iTasks lets you break work into multiple levels, keep the shared project context, and inspect the structure from both the task details screen and the project tree.
1. Creating a subtask
Open the parent task and press Subtask. The new card inherits the project and base parameters from its parent, so the project field is locked. If the parent task has a sprint, child tasks follow that context as well.
2. Nesting depth
iTasks supports up to four levels in total: the root task plus three subtask levels. This is enough to split complex work without turning the task into an unlimited structure where the next owner is hard to find.
3. What the subtask list shows
Inside the parent task, each subtask shows its title, status, assignee, and child count. Opening a subtask gives it a normal task screen with its own description, comments, attachments, status, and history.
4. Project tree
The project mode on the main screen shows the task hierarchy inside each project. It is useful for seeing the whole branch: website launch preparation, mobile menu checks, navigation on iPhone, and the menu in landscape orientation.
Switching main screen modes is covered in Task View Modes. Project configuration is covered in Projects.
Complete a task with subtasks
If unfinished regular subtasks remain anywhere below a parent task you are completing, iTasks lists them and asks you to confirm completing them together. Check the titles and current statuses. After confirmation, the listed subtasks are also completed; cancelling leaves the statuses unchanged.
Subtasks linked to a workflow are completed through their own workflows and are not completed by this action. Regular subtasks below them may still appear in the confirmation list. Check the displayed list, not just the nearest level of the tree.
Practical rule
Create a subtask when part of the work has its own assignee, due date, status, or discussion. If it is only a checklist item without an independent owner, it often belongs in the task description.
If multiple people need to work on the same task one after another, use a workflow with a sequence of assignees: each stage passes the task to its configured person. There is one current assignee, while the task card, files, and discussion stay together. Subtasks suit separate pieces of work, including parallel work; a workflow suits sequential handoffs of the same task.