What a subtask is and why you'd create one

A subtask in Jira is a smaller piece of work that belongs to a larger task. Think of it like breaking a to-do list item into smaller steps. If your main task is "Build login page," you might create subtasks for "Design the form," "Write the backend code," and "Test on mobile." Each subtask can be assigned to a different person, tracked separately, and marked complete on its own timeline.

Subtasks let you see the actual work underneath a big task. Instead of one person saying "the login page is done" when it really isn't, you can see that the form is done, the code is 80% done, and testing hasn't started. This is especially useful when multiple people are working on the same task or when you need to break down work that will take weeks.

Key Takeaways

  • Open the task you want to break down, scroll to the bottom, and click "Create subtask" — you do not need to leave the task to make one.
  • Give each subtask a clear name that describes one piece of work, assign it to someone, and set a due date if your team uses them.
  • Subtasks inherit the project from their parent task, so you do not have to pick a project again.
  • You can see all subtasks at a glance on the parent task's page, and each one shows its status so you know what is blocked or done.

Opening the task and finding the subtask button

Start by opening the task you want to break down. Click on the task name or ticket number from your board or search results — it will open in a detail view that shows everything about that task on the right side of your screen or in a full page, depending on your Jira setup.

Scroll down to the bottom of the task details. You will see a section labeled "Child issues" or "Subtasks" (the exact label depends on your Jira version). Below that section is a button or link that says "Create subtask." Click it. A form will appear where you enter the details of the new subtask.

Filling in the subtask details

The form asks for a Summary — this is the name of the subtask. Write something specific about what work needs to happen. "Code the login form" is better than "Work on login." The summary is what your team will see on the board and in lists, so make it clear enough that someone can start working without asking questions.

Next, you will see a field for Assignee. Click it and pick the person who will do this work. If you do not know yet, you can leave it blank and assign it later. Below that is usually a Due Date field — fill this in if your team tracks important date. Some teams skip this for subtasks and only set due dates on the parent task, so check what your team does.

You may see other fields like Priority, Story Points, or Labels. These are optional. If your team uses them, fill them in. If you are not sure, leave them blank — you can add them later by editing the subtask. The project is already set to match the parent task, so you do not need to pick one.

Saving the subtask and creating more

At the bottom of the form, click the "Create" button. The subtask will be created and added to the parent task. You will see it appear in the "Child issues" section on the parent task's page, usually with a status of "To Do" or "Open."

If you need to create more subtasks for the same parent task, the form usually stays open or resets. You can fill in the next subtask's details and click "Create" again. This is faster than closing the form and reopening it each time. Once you are done creating subtasks, close the form by clicking outside it or pressing Escape.

Assigning and tracking subtasks

After you create a subtask, you can click on it to open its details and make changes. If you left the assignee blank, click the "Assignee" field and pick someone now. You can also change the due date, priority, or any other field the same way you would on a regular task.

As work happens, the subtask's status will change. When someone starts work, they move it to "In Progress." When it is done, they move it to "Done." You can see all the subtasks and their statuses right on the parent task's page, so you always know how much of the bigger task is actually finished. If a subtask is blocked, someone can move it to "Blocked" so the team knows to wait.

Viewing all subtasks in one place

The parent task's detail page shows every subtask in the "Child issues" section. You can see the name, status, and assignee of each one at a glance. Click any subtask to open it and see more details or make changes.

If you want to see subtasks across many tasks, use Jira's search or filter features. You can search for "issuetype = Subtask" to see all subtasks in your project, or filter by assignee to see all subtasks assigned to one person. This is useful when you want to know how much work one person has across all the parent tasks they are involved in.

Common mistakes and how to avoid them

The most common mistake is creating a subtask when you should create a separate task instead. Subtasks should be pieces of one larger task. If the work is independent or belongs to a different goal, create a regular task instead. A subtask for "Fix the login bug" under "Build login page" makes sense. A subtask for "Update the database schema" under "Build login page" does not, because the schema work affects other features too.

Another mistake is creating too many subtasks. If you have more than seven or eight subtasks under one task, the parent task is probably too big. Consider breaking it into multiple parent tasks instead. This keeps the work organized and makes it easier to see progress.

Finally, do not forget to assign subtasks. If a subtask has no assignee, no one knows it is their job. Even if you are not sure who should do it, assign it to someone and let them reassign it if needed. An unassigned subtask often gets overlooked.

Frequently Asked Questions

Can I create a subtask of a subtask?

No. Jira does not allow subtasks under subtasks — only one level deep. If you need more layers, you are probably breaking down the work too much. Step back and think about whether you need fewer, bigger subtasks instead.

What happens to subtasks if I delete the parent task?

The subtasks are deleted too. If you want to keep the work, move the subtasks to a different parent task before deleting the original one. You can do this by editing each subtask and changing its parent.

Can I move a subtask to a different parent task?

Yes. Open the subtask, find the "Parent" field, and click it to change which task it belongs to. The subtask will move to the new parent's list of child issues.

Do subtasks show up on the board the same way regular tasks do?

It depends on your board settings. Some teams configure their boards to show subtasks as separate cards. Others hide subtasks and only show parent tasks. Ask your Jira admin or check your board settings to see how your team uses them.

Can I set a different project for a subtask than its parent?

No. Subtasks always belong to the same project as their parent task. If you need work in a different project, create a regular task instead and link it to the parent task using the "Link" feature.