How to Add Subtasks in Jira: A Step-by-Step Process Guide
Struggling to track every piece of Jira work? Learn how to add subtasks in Jira, assign owners, and monitor progress. Read now to get started.
When a Jira issue contains several pieces of work, it can be hard to see who owns each task and what remains unfinished. A long issue description may explain the plan, but it won’t give every small task its own assignee or status. That makes progress harder to track and handoffs easier to miss.
Subtasks give you a practical way to break a parent issue into smaller, trackable pieces while keeping the work connected. But here's the truth: creating one is simple once you know where Jira hides the action and what to check if it isn’t available. Follow the steps below to add a subtask, assign it, and confirm it appears under the right parent issue.
How to Add a Subtask in Jira
Open the parent issue, choose Jira’s subtask or child-issue action, enter the work details, and create the issue. The exact button label can vary between Jira versions and project types.
Open the parent issue. Find the Jira issue that represents the larger piece of work, such as “Prepare product launch.” Open its issue view so Jira can attach the new task to the correct parent.
Find the subtask action. Look for Add a child issue, Create sub-task, or a similar option in the issue actions. In some Jira layouts, the action is inside the More menu.
Enter the subtask details. Add a clear summary, such as “Draft launch email.” Include a description when the assignee needs context, and set fields such as assignee, priority, or due date if they are available and useful.
Create the subtask. Review the parent and task summary, then submit the form. When you start from the parent issue’s subtask action, Jira should associate the new issue with that parent automatically.
Check the result. Return to the parent issue and confirm the subtask appears in its child-issue area. Open the subtask to verify its assignee and details, then update its status as work progresses.
For example, a parent issue called “Prepare product launch” might have subtasks for drafting the email, reviewing the landing page, and checking analytics. Each task has its own status, while the parent keeps the work grouped together.
What Jira Subtasks Are—and When to Use Them
A Jira subtask is a smaller issue connected to a parent issue. It lets you track a specific piece of work separately without losing its relationship to the larger task.
Use one when a task needs its own assignee, status, or progress update. For instance, “Update checkout flow” could have subtasks for design, implementation, and testing. A short action that takes only a few minutes may not need its own issue.
Here's why: subtasks make ownership visible. Instead of adding “Alex will test this” to a long description, you can create a testing subtask, assign it to Alex, and track its status directly.
A subtask is different from a linked issue. A subtask belongs beneath a parent in the issue hierarchy; a linked issue has a relationship such as “blocks” or “relates to” without becoming a child task.
Choose the Right Parent and Break Down the Work
Start with the issue that best represents the work as a whole. If the parent is too broad, its subtasks may become a second project plan. If it is too narrow, the parent-child relationship adds little value.
Try to give each subtask one clear outcome. For a parent called “Publish help center update,” useful subtasks might be “Write the troubleshooting section” and “Review links.” “Work on help center” is too vague to assign or verify.
Let me explain: a good subtask should answer two questions quickly: who owns it, and what will show that it is complete? If either answer is unclear, refine the summary or add a short description before creating it.
Set Useful Details and Keep Progress Visible
Use the fields that help someone act. A concise summary, a practical description, an assignee, and a relevant priority are often enough. Add a due date when timing affects other work.
For example, “Review landing page” is easier to understand when its description says which page to check and what approval is needed. The assignee can then update the subtask’s status without changing unrelated work on the parent.
Keep parent and child statuses meaningful. If implementation is complete but testing remains open, the testing subtask should show that unfinished work. Avoid marking every child issue complete just to make the parent look finished.
Understand Jira’s Issue Hierarchy
Subtasks sit below standard issues in Jira’s issue hierarchy. A parent issue may itself belong to a larger work item, such as an epic, depending on your project configuration.
A useful example is an epic for a product launch, a standard issue for preparing the launch email, and subtasks for drafting, editing, and approval. The subtask belongs to the standard issue, not directly to the epic.
Subtasks generally cannot have their own subtasks. If a child task needs several independently tracked pieces, consider whether it should be a standard issue or whether the parent work needs a different breakdown.
Troubleshoot Missing Subtask Options
If you can’t find a subtask action, first confirm that you opened a suitable parent issue. The option may not appear in every menu or issue view, so check the issue’s actions and child-issue area.
Still stuck? Your project configuration or permissions may affect which issue types and actions are available. Ask a Jira administrator to check whether subtask issue types are enabled and whether your account can create them.
Also check that you are using the right project and issue type. Jira screens can differ across project types and product updates, so an administrator can confirm the correct path for your setup.
ONES.com Solution for Connected Project Work
Value Proposition
ONES.com brings project management and knowledge management together in one platform powered by ONES Assistant. ONES Project is a Jira alternative for planning and tracking work; ONES Wiki provides a knowledge base as a Confluence alternative. The products are sold separately.
If your team needs to divide work into trackable tasks while keeping plans and team knowledge accessible, ONES.com offers a connected option. You can choose cloud or self-hosted deployment, including on-premise, private cloud, and air-gapped environments.
Core Capabilities
Work is difficult to break down: ONES Project supports project and task management, helping teams organize larger work into smaller pieces and track responsibility.
Existing Jira processes are hard to replace: Jira-compatible workflows help teams carry familiar practices into a Jira alternative.
Built-in reports are missing from day-to-day planning: Built-in reporting gives teams a way to review project progress without relying on extra reporting plugins.
Default fields don’t fit the team: Custom fields let teams capture information that matters to their work, such as review status or release area.
Approval steps are difficult to track: Custom workflows allow teams to shape work stages around their process, so an issue can move through relevant review steps.
Sprint planning needs clearer tracking: Sprint management helps agile teams plan and follow work within sprint cycles.
Repeated manual actions take time: Automation can handle recurring workflow actions, reducing repetitive effort for the team.
Teams rely on too many add-ons: Native capabilities can reduce plugin dependence, while full feature parity between cloud and self-hosted versions gives teams deployment flexibility.
Application Scenarios
A software team moving from Jira: A team can map familiar Jira workflows into ONES Project, then use custom fields, sprint management, and reporting to manage delivery. This can make the transition easier for people who already know Jira-style issue tracking.
A team with restricted network requirements: An organization that cannot use a public cloud service can consider ONES Project in an on-premise, private cloud, or air-gapped deployment. The self-hosted option retains feature parity with the cloud version.
A project team that needs related knowledge: A team can use ONES Project for work tracking and choose ONES Wiki separately for team knowledge. ONES.com also offers a free plan for up to 30 seats.
Common Challenges When Creating Subtasks
The Subtask Option Isn’t Visible
Problem: You open an issue but cannot find a create-subtask action. The option may be in a different menu, or the project configuration may restrict subtask creation.
Solution: Check the issue actions and child-issue area first. If the action is absent, ask a Jira administrator to review your permissions and the project’s subtask configuration.
The Parent Issue Is Wrong
Problem: A task appears beneath an unrelated issue, making ownership and progress confusing.
Solution: Start from the intended parent issue before creating the subtask. After creation, open the parent and verify the child appears in its issue hierarchy.
The Subtask Summary Is Too Broad
Problem: A summary such as “Do launch work” doesn’t tell the assignee what to finish.
Solution: Write a specific action and outcome, such as “Check signup form on mobile.” Add the necessary context in the description instead of packing several tasks into one issue.
Progress Is Hard to Interpret
Problem: The parent appears complete even though a subtask remains open, or the team cannot tell which piece is blocked.
Solution: Update each subtask as its own work changes. Review child statuses before closing the parent, and use a clear status to show when a task needs attention.
FAQs About Jira Subtasks
Can I create a subtask without opening the parent issue?
Jira’s standard subtask workflow connects the new issue to a parent, so creating it from the parent issue is the clearest approach. Some Jira setups may offer other ways to set the parent during creation, but the available fields depend on configuration. If you use another route, confirm the parent relationship after creating the issue.
What should I do if I can’t create a subtask?
Check that the issue is an eligible parent and look through its actions for a subtask or child-issue option. If you still can’t find one, ask your Jira administrator to verify your permissions and whether subtask issue types are enabled for the project. The exact settings and menu labels can vary by Jira setup.
Can a Jira subtask have its own subtasks?
Jira subtasks generally sit at the lowest level of the issue hierarchy and cannot have another subtask beneath them. If a subtask needs several separately assigned pieces, consider restructuring the work. You might use a standard issue for the larger work item and make each independently tracked task a subtask of that issue.
Should I use a subtask or a linked issue?
Use a subtask when a piece of work belongs directly to a parent issue and should appear within its hierarchy. Use a linked issue when two issues are related but should remain separate at the same hierarchy level. For example, a task that blocks another team’s work may be better represented with an issue link than as a subtask.
Can I assign a subtask to someone other than the parent’s assignee?
Yes, if your Jira project settings and permissions allow it. A subtask can have its own assignee, which is useful when different people handle research, implementation, and testing under one parent issue. Check the assignee field on the subtask after creation to make sure the work has the right owner.
Conclusion
To add a Jira subtask, open the parent issue, choose its subtask or child-issue action, enter a specific task summary, and create it. Then confirm the parent relationship and assign the work so progress stays visible.
When an issue feels too large to manage, breaking it into clear pieces can make ownership and next steps easier to see. Choose a parent that fits the work, keep each subtask focused, and review its status as the team moves forward.