The short answer
A subtask is a piece of work required to complete a task, story or bug. Atlassian describes subtasks as a way to break a standard work item into smaller chunks. A subtask always has a parent, and it cannot have children of its own.
Use subtasks when one ticket needs several steps that different people do, or that you want to tick off separately: build, test, update the help text. If a piece of work could be planned, delivered or prioritised on its own, it is probably its own ticket, not a subtask.
Where subtasks sit
By default Jira has three levels of work:
| Level | Work types | Can have children? |
|---|---|---|
| Epic | Epic | Yes: stories, tasks, bugs |
| Standard | Story, task, bug | Yes: subtasks |
| Subtask | Subtask | No |
Atlassian's help is explicit that a subtask cannot have child work items. So if a subtask grows into something that needs its own steps, turn it into a standard ticket instead.
Two different words get mixed up here. The stories and tasks under an epic are its child work items, not subtasks. Subtasks are the level below those. Picking between story, task and bug is covered in story vs task vs bug, and epics in what an epic is.
When subtasks help
- Several people work on one story. "PAY-142 Monthly statement as PDF" might have subtasks for the backend work, the screen and the tests, each assigned to the person doing it.
- You want a checklist the team can see. Each subtask moves through the workflow, so the parent shows how far the steps have got.
- Steps must all finish before the parent can. Atlassian's sprint help says all subtasks must be marked Done before a sprint can be completed, which makes open steps hard to miss.
When a subtask is the wrong choice
- It could ship on its own. If users would get value from it alone, make it a story or task so it can be planned and prioritised separately.
- It belongs to a different team. Work another team does is easier to track as its own ticket on their board, linked to yours (see how to link tickets).
- It is a bug found later. A bug found after the story is done is a new bug ticket, not a subtask of finished work.
- It would be the only subtask. One subtask that repeats the parent adds a click and nothing else.
How to create a subtask
Atlassian's steps for a company-managed space:
- Open the parent work item.
- Select Add or create related work below the summary, then choose Create subtask.
- Enter a summary and select Create.
In a team-managed space, the same menu offers Add a child work item. Atlassian notes that in team-managed spaces, subtasks can sit under stories, bugs and tasks but not directly under epics.
If you do not see the option, subtasks may be switched off. In company-managed spaces, an administrator has to enable subtasks and add the subtask work type to the space's work type scheme first.
Two other limits worth knowing: you cannot create a subtask from the board columns, and Atlassian notes you cannot convert a work item to a subtask if it has subtasks of its own.
Writing good subtasks
- Start the summary with a verb: "Write tests for PDF export", "Update help article". Someone scanning the parent should see the steps at a glance.
- Assign each one to the person who will do it, so the board shows who is doing what.
- Keep the details on the parent. The why and the acceptance criteria belong on the story; the subtask only needs what is specific to that step.
- Move them as you go. A subtask left in To Do after the work is done makes the parent look unfinished.
Subtasks on the board
A board can group subtasks under their parent. Atlassian's swimlane help describes a Stories swimlane option where each swimlane is one parent work item containing its subtasks, with work items that have no subtasks shown below. If your board is crowded with small cards, this setting can tidy it up; a board admin can change it.
Practise splitting and creating work
Getting the size of a ticket right comes with practice. Agile Board Practice has a lesson where you create a story and a bug on a practice board, choosing the type, priority and details, with feedback on each step.
Frequently asked questions
What is a subtask in Jira?
Atlassian defines a subtask as a piece of work required to complete a task. Subtasks break a story, task or bug into smaller chunks, and they cannot have children of their own.
What is the difference between a task and a subtask in Jira?
A task is a standard work item that can be planned on its own. A subtask always belongs to a parent story, task or bug and is one step toward finishing it.
Can a subtask have subtasks in Jira?
No. Atlassian's help says a subtask cannot have any child work items. If it needs its own steps, make it a standard ticket.
Why can't I create a subtask in Jira?
In company-managed spaces, an admin must enable subtasks and add the subtask work type to the space's work type scheme. You also cannot create a subtask from the board columns; open the parent instead.
Are the stories under an epic subtasks?
No. Stories, tasks and bugs under an epic are its child work items. Subtasks are the level below them.