How to Add a Subtask in Jira: A Step-by-Step Guide (2026)
Need to break down a Jira issue? Learn jira how to add subtask, verify its parent, and fix setup issues. Read now to get started.
A large Jira issue can quickly become difficult to track. One task may hide several separate pieces of work, making ownership unclear and progress hard to measure.
Creating subtasks seems simple, but the available controls can vary by Jira project and issue type. A missing permission or disabled subtask setting can also stop you midway.
Here’s how to add a subtask in Jira, check that it appears under the right parent, and avoid common setup problems. I’ll also explain when to split work and how a project platform can support clearer task breakdowns.
How to Add a Subtask in Jira
Open the parent issue, choose the subtask action, enter the required details, and create it. Then confirm the new issue appears beneath the correct parent.
Open the parent issue. Go to the Jira project and select the issue that represents the larger piece of work. For example, open “Launch customer portal” before adding subtasks for design, development, and testing.
Find the subtask action. In the issue view, open the More menu or the issue actions menu. Choose Create sub-task or the equivalent option shown in your Jira interface.
Enter the subtask details. Add a clear summary describing one specific piece of work. Fill in any required fields, such as assignee, priority, description, or due date.
Create the subtask. Select the create button in the dialog. Jira should create a separate issue linked beneath the parent issue.
Check the issue hierarchy. Return to the parent issue and look for the subtask in its child issues or subtasks area. Open it once to confirm the summary and assignee are correct.
But here’s the truth: If you don’t see a subtask option, your Jira project may not allow subtasks, or your account may lack permission. Check the troubleshooting section below before trying another route.

What a Jira Subtask Is—and When to Use One
A subtask is a smaller Jira issue linked to a parent issue. It lets you divide a broader piece of work into manageable parts while keeping those parts connected.
For example, a parent issue called “Prepare product launch” could have subtasks for writing release notes, checking analytics, and preparing customer support. Each subtask can have its own assignee and status.
Here’s why: the parent gives the team a view of the overall outcome, while the subtasks show who is handling each part. This makes the work easier to coordinate without losing the connection between related tasks.
Use subtasks when work belongs to one larger issue and needs distinct owners or steps. If a piece of work needs its own planning, reporting, or release tracking, a separate standard issue may be a better fit.
Choose the Right Subtask Details
A useful subtask summary starts with a clear action. “Test checkout on mobile” tells a teammate more than “Mobile” or “Testing.”
Let me explain: subtasks are easiest to manage when each one describes a specific result. For a website redesign, “Review tablet navigation” is more actionable than “Review design.”
Add an assignee when someone is responsible for completing the work. Include acceptance details in the description if the task could be interpreted in different ways, such as which screen sizes or browsers need testing.
Keep the number of subtasks practical. If a parent issue has a long list of tiny actions, combine related work or reconsider whether the parent should be split into separate issues.
Understand the Parent-and-Child Relationship
A subtask remains connected to its parent, which helps teammates understand the larger goal. For instance, a development subtask can sit beneath a parent issue describing a new checkout feature.
The parent and subtask do not always follow identical workflows. A subtask may move through its own statuses, while the parent’s progress depends on your project’s configuration and team conventions.
The best part? This hierarchy can reduce context switching. A teammate can open the parent to see the broader objective, then open a child issue for its owner, status, and details.
Before creating several subtasks, agree on how your team will use them. A simple rule—one subtask per distinct owner or deliverable—can make the issue hierarchy easier to scan.
Check Permissions and Project Settings
If the create-subtask action is missing, check whether subtasks are enabled for the project and whether your account has the required permissions. A Jira administrator may need to review the configuration.
Jira screens and labels can differ across project types and interface versions. One project may show the action in a More menu, while another may place it elsewhere in the issue view.
You might be wondering: can every Jira issue have a subtask? The available issue types and hierarchy rules depend on the project’s configuration. If a specific issue cannot have a child issue, ask your administrator to check the project setup.
For example, if one teammate can create subtasks but another cannot, that points to a permission difference. If nobody can find the action, review the project configuration and enabled issue types.
Make Subtasks Easier to Track
Agree on a naming pattern that describes the action and outcome. A team working on a release might use “Verify upgrade path” and “Update launch checklist” instead of vague labels.
Give each subtask a clear owner when possible. If several people share responsibility, specify who is coordinating the work and explain any handoffs in the description.
Use status updates to show real progress, not just activity. Moving a subtask forward after its work is complete gives teammates a more reliable view than leaving every child issue open until the parent is finished.
Review the parent issue during planning or team check-ins. If the subtasks no longer reflect the work, update them so the hierarchy remains useful rather than becoming a second, outdated task list.
Value proposition: ONES.com brings project management and knowledge management together in one platform powered by ONES Assistant. ONES Project is its project management product and a Jira alternative; ONES Wiki is a knowledge base product and a Confluence alternative. They are sold separately.

When you break a large issue into smaller tasks, the team also needs clear ownership, consistent workflows, and a place to explain decisions. ONES Project can support that work with Jira-compatible workflows and built-in project capabilities.
Core Capabilities
Issue tracking feels fragmented → ONES Project provides project management in a unified platform → Result: teams can organize project work in a consistent environment.
Existing Jira processes are difficult to replace → Jira-compatible workflows help teams carry familiar process patterns into ONES Project → Result: teams can adapt their workflows without starting from scratch.
Standard workflows do not match the team’s steps → Custom workflows let teams shape how work moves through stages → Result: issue progression can reflect the team’s actual process.
Default fields miss important details → Custom fields let teams capture relevant project information → Result: work items can include details the team needs to coordinate.
Progress is difficult to review → Built-in reporting gives teams project information to review → Result: managers and contributors can discuss progress with a shared view.
Sprint planning needs structure → Sprint management supports teams that organize work into sprints → Result: sprint work can be planned and followed within the project environment.
Repeated steps take manual effort → Automation can handle selected workflow actions → Result: teams can reduce repetitive coordination work.
Too many add-ons complicate administration → Native capability parity and built-in functions can reduce reliance on plugins → Result: teams may manage more of their routine project work within the platform.
Application Scenarios
Product development: A team can organize feature work into assigned tasks, manage sprint activity, and use custom workflows for review and testing. That can help keep contributors aligned as work moves toward release.
Restricted or self-hosted environments: Teams can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment. ONES.com offers full feature parity between its cloud and self-hosted versions, giving organizations deployment flexibility without a separate feature set.
Project and knowledge management: A team can use ONES Project for project work and, separately, ONES Wiki for knowledge management. The products serve different needs, so teams can select either or both.
ONES.com offers a free plan for up to 30 seats. If your team is considering a Jira alternative, compare its workflow needs, deployment requirements, and plugin use before deciding whether it fits.
Common Challenges When Creating Jira Subtasks
The Subtask Option Is Missing
Problem: You open the issue actions menu but cannot find a subtask command.
What to do: Check whether subtasks are enabled for the project and confirm your account has the necessary permissions. Ask a Jira administrator to review the project configuration if you still cannot see the action.
The New Issue Appears in the Wrong Place
Problem: You create a subtask but cannot find it beneath the expected parent.
What to do: Reopen the parent issue and inspect its subtasks or child issues area. Confirm you started the creation process from the correct parent before creating another issue.
The Subtask Is Too Vague
Problem: A title such as “Review” does not explain what needs to happen or when the work is finished.
What to do: Rewrite the summary as an action with a clear outcome, such as “Review payment errors on mobile.” Add completion details when the expected result needs clarification.
The Parent Issue Has Too Many Subtasks
Problem: The parent becomes crowded with small actions, making it harder to spot important work.
What to do: Combine closely related actions or create separate standard issues for work that needs independent planning and tracking. Keep subtasks focused on pieces that belong to the same parent outcome.
FAQs About Jira Subtasks
Can I add a subtask to any Jira issue?
Not necessarily. Whether you can create a subtask depends on the project’s configuration, available issue types, and your permissions. Open the parent issue and check its actions menu. If the subtask option is missing, ask a Jira administrator to verify that subtasks are enabled and that your account can create them.
Can a Jira subtask have its own assignee and status?
Yes, a subtask can have its own details, including an assignee and status, when those fields are available in your project. This lets a team assign one part of a larger task to a specific person. Project workflows determine which statuses are available, so the subtask’s progress may not match the parent’s status.
What should I do if I cannot see “Create sub-task”?
Look in the issue’s More menu or its other actions menu first, since Jira’s layout can vary. If the option is still missing, check whether the project supports subtasks and whether you have permission to create them. An administrator can review the project setup and access rules.
When should I create a separate issue instead of a subtask?
Create a separate issue when the work needs independent planning, reporting, or tracking beyond the parent’s scope. Use a subtask when the work is a distinct part of one larger issue and should remain connected to it. For example, a focused testing activity may fit beneath a feature, while a separate release effort may need its own issue.
Conclusion
To add a Jira subtask, open the parent issue, choose the subtask action, enter a clear summary and required details, then confirm the child issue appears beneath the right parent.
Use subtasks for distinct pieces of work that belong to one larger outcome. Clear ownership, specific summaries, and a quick hierarchy check can prevent confusion later.
If the option is missing, check permissions and project settings before changing your workflow. And if your team is evaluating another way to manage project work, compare its workflow, deployment, and reporting needs with platforms such as ONES.com.