How to Create a Subtask in Jira: A Step-by-Step Process
Struggling to organize smaller tasks? Learn how to create subtask in Jira, link it to the right parent, and fix setup issues. Read now.
To create a subtask in Jira, open the issue that will act as its parent, choose the subtask action, enter a summary, and save. The new item then appears beneath the parent issue, giving you a clear way to track a smaller piece of work.
But here's the truth: the option can be hard to spot, and Jira’s menus may look different across projects. Choosing the wrong issue type or parent can also make work harder to organize. Here’s how to create a subtask, check that it is linked correctly, and solve common setup problems. I’ll also explain when subtasks help—and when a separate issue may be a better fit.
How to Create a Subtask in Jira
Start from the issue you want to break down. In Jira, a subtask needs a parent issue, so opening that parent first helps keep the relationship clear.
Open the parent issue. Find the Jira issue that represents the larger task, such as “Prepare the product launch.” Open its detail view.
Open the issue actions. Select the three-dot menu or the available issue actions menu. Depending on your Jira layout, you may see an option such as Create sub-task or Add a child issue.
Choose the subtask action. If Jira asks you to select an issue type, choose a subtask type available in your project. The wording and available types can vary by project configuration.
Enter the subtask details. Add a short summary, such as “Draft launch email.” Fill in any required fields, including assignee, priority, or due date, if they apply.
Save the subtask. Select Create or the equivalent button. Jira should return you to the parent issue or show a confirmation.
Check the parent relationship. Look for the new subtask in the parent issue’s child issues or subtasks area. Open it to confirm its summary, status, and assignee.
Here’s why that final check matters: a task with the right summary but no visible parent may not be the subtask you intended to create. Confirm the relationship before moving on.
Example: Break a larger task into smaller actions
Say the parent issue is “Prepare the product launch.” You could create subtasks for “Draft launch email,” “Review landing page,” and “Confirm release notes.” Each subtask represents a specific action tied to the same larger piece of work.
Keep each summary clear enough to understand without opening the issue. “Check email” is vague; “Review launch email for final approval” gives the assignee a more useful next step.
When to Use a Subtask Instead of a Separate Issue
A subtask is useful when work belongs inside one parent issue and can be tracked as a smaller activity. For example, a feature issue might have subtasks for implementation, testing, and a design review.
A separate issue may fit better when work needs its own place in planning, reporting, or prioritization. If a task can be completed independently or has a different owner and timeline, ask whether it should stand alone instead of sitting beneath another issue.
The best part? You don’t need to split every issue. If “Update a typo” is already small and clear, adding another layer may create extra tracking without improving visibility.
A quick decision check
Use a subtask when the work supports one parent issue and the team wants to track the pieces separately.
Use a separate issue when the work needs independent planning, prioritization, or visibility.
Keep the parent as-is when the work is already clear and small enough to manage.
How to Confirm the Subtask Is Set Up Correctly
After creating a subtask, check its connection to the parent, its issue type, and its key details. This quick review can catch problems before the team starts work.
Check the parent view. The new subtask should appear in the parent issue’s subtasks or child issues area.
Open the subtask itself. Confirm that the summary describes one action and that the issue type is a subtask type.
Review ownership and status. Check the assignee and workflow status. If your team uses a due date or priority, confirm those fields too.
Look at the parent’s progress. Jira may show subtask status or progress alongside the parent. The exact display depends on the project and view.
For example, if “Review landing page” is assigned to the design reviewer, make sure it appears under the launch parent and has the expected status. That gives teammates a better view of what remains.
Why the Subtask Option Might Be Missing
If you can’t find the subtask action, start with the issue view and project setup. Jira menus differ, and available actions can depend on your permissions and configuration.
You’re looking at the wrong issue view. Open the issue itself rather than relying on a compact board card. The full detail view usually exposes more actions.
Your project doesn’t offer the option in that menu. Check for a child-issue action or another issue creation option. Labels can differ between Jira layouts.
You lack permission. Ask a project administrator whether your role can create issues or subtasks in that project.
The issue type isn’t available. Project configuration may affect which types can be created. Ask an administrator to check the project’s issue type setup.
Let me explain: repeatedly clicking through menus won’t fix a permission or configuration issue. If the action is missing after you open the parent issue, ask your Jira administrator to check access and project settings.
Managing Subtasks Across a Team
Subtasks work best when the team agrees on how much to break work down. If one person creates a separate subtask for every tiny action, the parent can become harder to scan than the original issue.
For example, a team could use subtasks for work that has a distinct owner or completion state, such as “Write test plan” or “Validate mobile layout.” Small actions that don’t need independent tracking can stay in the parent issue’s description or checklist.
Agree on simple naming and ownership habits. A useful subtask summary starts with an action, while a clear assignee shows who is responsible. During planning, review whether the subtasks still reflect the work the team needs to track.
Jira-Style Project Workflows with ONES.com
When a team needs Jira-like project workflows alongside knowledge management, ONES.com offers a unified platform with separate products. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge management product and a Confluence alternative. They are sold separately.
ONES.com may be worth evaluating if your team is reviewing how it organizes work, wants to reduce reliance on plugins, or needs a self-hosted deployment option. Its project management capabilities include Jira-compatible workflows, sprint management, automation, custom workflows and fields, and built-in reporting.
Core capabilities: common needs and possible outcomes
Need to adapt Jira-style workflows: ONES Project supports Jira-compatible workflows. Your team can evaluate whether those workflows fit its existing process.
Need to track work in sprints: Sprint management supports planning and organizing work into sprint cycles.
Need fields that reflect your process: Custom fields let teams capture details relevant to their work instead of relying only on default fields.
Need a workflow that matches team steps: Custom workflows let teams shape process stages around their way of working.
Need visibility into progress: Built-in reporting can help teams review project activity without depending on separate reporting plugins.
Need to reduce plugin reliance: Core project capabilities are available within ONES Project, which can reduce the number of added plugins a team needs to assess.
Need controlled deployment choices: ONES.com is available as Cloud, On-Premise, Private Cloud, and Air-gapped deployments.
Need the same capabilities in a self-hosted environment: ONES.com states that its cloud and self-hosted versions have full feature parity.
Where teams might apply it
A software team that plans work in sprints could evaluate ONES Project’s workflow, sprint, and reporting capabilities while reviewing its project process. A team with restricted network requirements could compare its deployment options, including On-Premise or Air-gapped setups.
A team that also wants a knowledge management product can assess ONES Wiki separately from ONES Project. The two products address different needs, so you can evaluate the project and knowledge management requirements independently.
ONES.com offers a free plan for up to 30 seats. If your team is considering a Jira alternative, compare the workflow needs, deployment requirements, and plugin reliance that matter in your environment before choosing a platform.
Common Challenges When Creating Subtasks
Subtasks are too small to manage
Problem: A parent issue accumulates many tiny subtasks, making the work difficult to scan. Solution: Create a subtask only when the activity needs distinct ownership, status, or visibility.
The subtask has an unclear summary
Problem: A title such as “Fix it” leaves the assignee guessing. Solution: Use an action and a specific outcome, such as “Update the checkout error message.”
The wrong parent was selected
Problem: The subtask appears under an unrelated issue. Solution: Create it from the intended parent, then verify the relationship in that issue’s subtask area.
The create action is unavailable
Problem: You can’t see a subtask option or Jira rejects the creation attempt. Solution: Confirm the issue view, then ask a project administrator to review your permissions and project configuration.
Frequently Asked Questions
Can a Jira subtask have its own subtasks?
No. Jira subtasks sit beneath a parent issue and can’t have another layer of subtasks beneath them. If a piece of work needs its own breakdown, consider whether it should be a separate issue. Then discuss how your team will link or organize that work so its relationship to the original issue remains clear.
Can I create a Jira subtask without opening the parent issue?
The clearest method is to open the parent issue and create the subtask from its actions. That helps Jira connect the new item to the intended parent. Available creation options can vary by project and Jira layout, so check your project’s issue view if you don’t see the expected action.
Can I change a regular Jira issue into a subtask?
Jira may provide issue type or move actions, but whether you can convert an issue depends on your project setup and permissions. Before changing an existing issue, check that it can be moved under the intended parent and that its fields and workflow will remain appropriate. Ask a project administrator if the conversion action isn’t available.
Why can’t I create a subtask in Jira?
The action may be hidden in a different menu, unavailable for your issue type, or restricted by project permissions. Open the parent issue’s full detail view and look for a subtask or child-issue action. If it remains missing, ask a project administrator to check your access and the project’s issue type configuration.
Should every task be a subtask?
No. A subtask is most useful when a smaller piece of work belongs to a parent issue and needs separate tracking. If the work can be prioritized or managed independently, a separate issue may be a better fit. For a simple action that needs no separate owner or status, keep it with the parent issue.
Conclusion
To create a subtask in Jira, open its intended parent, use the available subtask action, enter the key details, and save. Then check that the new item appears under the correct parent with the right type, owner, and status.
Keep the breakdown practical: create subtasks when they improve ownership or visibility, and avoid adding layers for work that is already clear. If the action is missing, check your Jira view and ask an administrator about permissions or project configuration. When your team reviews its wider project workflow, ONES Project is one Jira alternative to evaluate alongside your deployment and reporting needs.