Jira Tasks and Subtasks: A Step-by-Step Workflow Explained
Unsure when to use Jira tasks and subtasks? Follow a step-by-step workflow to organize work and track progress. Read now to get started.
A Jira task can look simple until one piece of work turns into five separate actions. If the team tracks every action as its own top-level issue, priorities and progress become harder to follow.
That confusion grows when people are unsure whether to create a task, a subtask, or both. Work may be duplicated, hidden under the wrong parent, or left without a clear owner.
Here’s the truth: a task describes a piece of work, while subtasks break that work into smaller, trackable parts. I’ll walk you through a practical Jira workflow for choosing the right level, creating subtasks, assigning responsibility, and tracking progress without adding unnecessary overhead.
A Step-by-Step Workflow for Jira Tasks and Subtasks
Start with the outcome you need to deliver. Create a Jira task for a meaningful, independently trackable piece of work, then add subtasks only when smaller actions need their own owners or progress tracking.
- Define the outcome. Write one sentence that explains what should be finished. For example: “Publish the updated billing page.”
- Choose the right issue level. Use a task when the work can be planned and tracked on its own. Use a subtask when the work belongs inside a larger parent issue.
- Break down the work only where useful. For the billing page, subtasks might include “Update page copy,” “Review with legal,” and “Test on mobile.”
- Create the parent issue. Add a clear summary, useful details, priority, and an assignee or team owner. Include acceptance criteria so everyone knows what “done” means.
- Add and assign subtasks. Create a subtask from the parent issue, give it a specific outcome, and assign someone who can complete it. Add an estimate if your team uses estimates.
- Review the workflow and progress. Check that each subtask has a meaningful status and that the parent issue reflects the team’s agreed process. Update progress during normal planning and check-ins.
For example, “Publish the updated billing page” is the parent task. Copy, legal review, and mobile testing are subtasks because they contribute to that single outcome.

What Jira Tasks and Subtasks Mean
In Jira, a task is an issue type teams use to represent work. A subtask is a child issue linked beneath a parent issue, giving a larger piece of work smaller, separately trackable parts.
Here’s why the distinction matters: a task can stand on its own in the team’s plan. A subtask belongs to its parent and helps show who is doing each part of that parent’s work.
Use a task for independently managed work
A task makes sense when the work needs its own place in a backlog, sprint, or team plan. For example, “Prepare the quarterly accessibility review” could be a task if it has its own owner, priority, and delivery target.
It can still contain subtasks if the team needs to coordinate separate actions. The key question is whether those actions are parts of one outcome or separate deliverables that should be planned independently.
Use a subtask for work that belongs to a parent
A subtask is useful when someone needs to track a distinct part of a parent issue. In a website redesign, “Check keyboard navigation” might be a subtask beneath “Complete accessibility review.”
Subtasks help clarify ownership and progress, but they also add more issues to maintain. If a task has only one person and one straightforward action, a subtask may create more tracking than value.
Plan the Right Level of Detail
Before creating issues, decide how the team will recognize a useful task and a useful subtask. A clear rule prevents one person from tracking every small action while another keeps the entire project in a single issue.
Try this test: can the work be prioritized, assigned, or completed independently? If yes, a separate task may be appropriate. If it only makes sense as part of a parent outcome, a subtask is usually clearer.
Keep issue summaries specific
“Fix the checkout” is too broad to guide a teammate. “Show an error when a payment card is declined” describes a more concrete outcome and gives the assignee a clearer starting point.
Use summaries that describe the result, then add context and acceptance criteria in the issue details. For example, a subtask called “Test declined-card message” can specify the expected message and the payment scenario to check.
Break work into manageable pieces
A subtask should be small enough for someone to understand and update, but meaningful enough to deserve separate tracking. “Review product copy” may be useful; “Open the review page” usually is not.
Think of the parent as a short project brief and its subtasks as the coordinated actions needed to deliver it. If a subtask grows into an independently planned outcome, discuss whether it should become a separate task.
Create, Assign, and Update Issues in Jira
Jira’s exact labels and menus can vary by project type and configuration. In general, open the parent issue and use its available action for creating a child issue or subtask.
Let me explain: the important part is not a particular button name. It’s confirming that the new issue appears under the intended parent, has the right issue type, and contains enough detail for its assignee to act.
Check your project’s configuration
If you cannot create a subtask, check whether your project permits subtasks and whether your account has the necessary permissions. An administrator may need to review the project’s issue types or access settings.
Some teams configure different workflows or required fields for different issue types. A subtask may therefore ask for information that the parent task does not require.
Give each subtask a clear owner and next action
Assign an issue to someone who can move it forward, and make the next action easy to understand. “Check the new checkout on a phone” is more useful than “QA.”
If work is shared, agree on one accountable assignee and describe who else needs to contribute. This gives the team a clear person to contact when the issue is blocked.
Update status as work changes
Move issues through the statuses your team uses, such as To Do, In Progress, and Done. Add a short comment when the status change needs context, such as a test result or a dependency.
Do not assume that completing every subtask automatically completes the parent. Jira behavior can depend on workflow configuration, so check the parent’s status and update it when the team’s completion criteria are met.
Track Parent Progress Without Losing Context
Subtasks make ownership visible, but the parent issue still needs attention. A parent can remain open after its child issues are done if a review, approval, or final check remains.
For example, a “Release help center update” task might have subtasks for writing, editing, and publishing. The parent is not ready to close until the release has been checked in the live environment.
Use parent issues for outcomes and subtasks for progress
Keep the parent’s description focused on the finished outcome and the conditions for completion. Use subtasks to show the work in progress, who owns it, and what remains.
When your team reviews a sprint or backlog, check both levels. A parent summary gives a quick view of the goal, while the subtasks help explain delays and handoffs.
Make blockers visible early
If a subtask depends on a decision, access, or another team’s work, note that dependency before it becomes a surprise. A brief status update can explain what is blocked and who needs to respond.
For instance, a design review might be waiting for a product decision. Recording that on the relevant issue helps the team distinguish blocked work from work that has not started.
Common Mistakes to Avoid
Small Jira habits can make a workflow harder to use. These common problems are easier to correct when the team agrees on a simple standard.
- Creating subtasks for every tiny action: Too many issues add maintenance work. Create a subtask when separate ownership or progress tracking will help.
- Making a subtask act like a separate deliverable: If the work needs independent prioritization or planning, consider a standalone task instead.
- Using vague summaries: Replace labels like “Update” with a specific result, such as “Update the refund instructions on the billing page.”
- Leaving the parent untouched: Review the parent status and completion criteria even after its subtasks are finished.
- Assuming every Jira project behaves the same: Project configuration, permissions, and workflows can differ. Confirm the setup with your Jira administrator when an action is unavailable.
ONES.com Solution for Teams Managing Project Work
ONES.com brings project management and knowledge management together in one platform, powered by ONES Assistant. ONES Project handles project work as a Jira alternative, while ONES Wiki provides knowledge management as a Confluence alternative; the products are sold separately.

The platform may suit teams that want Jira-compatible workflows, built-in reporting, and self-hosting choices. The free plan supports up to 30 seats, and deployments include Cloud, On-Premise, Private Cloud, and Air-gapped options.
Core capabilities
- Pain: Different teams need different issue structures. ONES capability: Custom workflows and fields. Result: Teams can shape issue tracking around their work.
- Pain: Sprint planning gets scattered across manual steps. ONES capability: Sprint management. Result: Teams can plan and review sprint work within the project workflow.
- Pain: Progress is difficult to see across issues. ONES capability: Built-in reporting. Result: Teams can review project progress without relying on add-on reporting tools.
- Pain: Repeated actions slow down routine work. ONES capability: Automation. Result: Teams can reduce repetitive workflow steps.
- Pain: Jira teams need familiar process patterns. ONES capability: Jira-compatible workflows. Result: Teams can work with familiar structures while evaluating another platform.
- Pain: Plugin dependencies increase administration. ONES capability: Native project features, including reporting and workflow customization. Result: Teams may be able to reduce reliance on plugins for those needs.
- Pain: Some organizations need control over where their system runs. ONES capability: On-Premise, Private Cloud, and Air-gapped deployments. Result: Teams can choose a deployment aligned with their environment.
- Pain: Self-hosted teams worry about feature gaps. ONES capability: Full feature parity between cloud and self-hosted versions. Result: Teams can choose deployment type without giving up the stated feature set.
Application scenarios
A software team can use ONES Project to organize sprint work, assign owners, and customize workflows for its issue types. A team that has relied on Jira can assess Jira-compatible workflows while reviewing its need for reporting and plugins.
An organization with restricted network requirements can consider an Air-gapped or other self-hosted deployment. If it also wants a dedicated knowledge management product, ONES Wiki is available separately from ONES Project.
Common Challenges and Practical Fixes
Subtasks are unavailable
Problem: The option to create a subtask does not appear. Fix: Ask a Jira administrator to check project permissions and whether subtasks are enabled for that project.
The parent and subtasks use different workflows
Problem: A child issue cannot move through the same statuses as its parent. Fix: Confirm the workflow assigned to each issue type, then agree on how the team should track progress across both levels.
People are unsure what “done” means
Problem: A task reaches Done, but reviewers disagree about whether the result is complete. Fix: Add acceptance criteria to the parent and clarify any required checks in the relevant subtasks.
Too many issues make planning noisy
Problem: The team spends more time updating small subtasks than delivering work. Fix: Keep subtasks for work that needs separate ownership, estimation, or status tracking. Combine minor actions in the parent description when appropriate.
FAQs
Can a Jira subtask exist without a parent?
A Jira subtask is designed to belong to a parent issue, so it is not intended to serve as an independent task. If the work needs its own priority, planning, or lifecycle, create a standalone issue type instead. The exact options available depend on your project configuration, so check with your Jira administrator if the issue hierarchy behaves differently.
Can a Jira subtask have its own subtasks?
Jira’s standard issue hierarchy does not generally support creating a subtask beneath another subtask. If a piece of work needs another level of breakdown, consider whether it should be represented as a separate task or handled through your team’s configured hierarchy. Confirm the available structure in your Jira project before planning work that depends on multiple nested levels.
Does completing every subtask automatically complete the parent?
Not necessarily. Parent status changes can depend on the workflow and automation rules configured for your Jira project. Even when all subtasks are complete, the parent may still need a final review, approval, or release check. Agree on the completion criteria and verify the parent status rather than assuming Jira will update it automatically.
Should I estimate subtasks or only the parent task?
That depends on how your team plans and reports work. Estimating subtasks can help when separate owners need to plan their effort or the team tracks progress at that level. If your team estimates only parent issues, adding estimates to every subtask may create duplicate or confusing totals. Choose one approach and apply it consistently.
Can Jira tasks and subtasks use different workflows?
They can follow different workflows when the project configuration assigns different workflows to their issue types. That may be useful when subtasks need a simpler path, but it can also make parent progress harder to interpret. Review the available statuses and transitions with your Jira administrator, then make sure the team understands how child work relates to the parent’s status.
Conclusion
Jira tasks and subtasks work best when each level has a clear purpose. Give a task an outcome the team can plan independently, and use subtasks for distinct actions that need their own owners or progress updates.
Keep summaries specific, check your project’s workflow, and review the parent after its subtasks are complete. That simple approach reduces confusion and keeps planning focused on delivery. When issue tracking starts creating more overhead than clarity, revisit how much work you break down and whether your workflow still fits the team.