Jira Issue to Subtask Conversion: A 5-Step Process Guide
Need to reorganize Jira work? Learn the jira convert to subtask process in 5 steps, from choosing a parent to mapping fields. Read now.
Have you ever created a Jira issue as a task, then realized it belongs under a larger piece of work? Leaving it at the wrong level can muddy your backlog, sprint plan, and progress reports.
Changing the hierarchy can feel risky, especially when the issue already has comments, estimates, or links. A rushed conversion may also leave you with an unexpected parent or a status that needs attention.
But here's the truth: Jira can convert an eligible issue into a subtask through a guided process. You’ll need to choose a valid parent, check the fields Jira asks you to map, and confirm the result afterward. Here’s a practical five-step walkthrough, plus checks that help you avoid common snags. The exact labels may vary slightly between Jira versions, but the key decisions remain the same.
How to Convert a Jira Issue to a Subtask in 5 Steps
In short, open the issue’s action menu, choose the subtask conversion option, select a parent, review the required fields, and verify the converted issue. Make sure your project supports subtasks before you begin.
-

1. Confirm the issue can become a subtask
Open the issue and check that it is currently a standard issue type, such as a task or bug. Subtasks sit beneath a parent issue, so you’ll need a suitable parent in the same project context.
Check with your Jira administrator if you can’t find a subtask issue type or conversion option. Subtasks may be disabled for the project, or the available issue types and permissions may restrict the change.
-
2. Open the issue actions
Go to the issue you want to convert. Open its actions menu, often shown as three dots or labeled More, and look for Convert to sub-task or a similar option.
If the option is missing, don’t assume the issue is broken. Check your project permissions, issue type configuration, and Jira version. An administrator can help identify which setting or restriction applies.
-
3. Select the parent issue
Choose the issue that should contain the new subtask. For example, if you’re breaking “Launch a help center” into smaller pieces, “Write article templates” could become a subtask beneath that launch issue.
Pick a parent that represents the work the subtask supports. A mismatched parent can make the backlog harder to read and can affect how the team plans or reports progress.
-
4. Review the issue type and field changes
Jira may ask you to select a subtask type, map fields, or resolve fields that aren’t available for the new issue type. Review the summary, description, assignee, priority, estimates, and any required custom fields shown on the conversion screen.
Pay close attention to fields that may change or need a new value. For instance, a custom field used on standard tasks might not be available on subtasks. Complete the required fields before moving on.
-
5. Complete the conversion and verify the result
Confirm the conversion, then open the issue again. Check that it appears under the correct parent, has the expected issue type, and retains the key details your team needs.
Review comments, links, estimates, attachments, and status as appropriate for your Jira setup. If anything looks wrong, check the issue history and ask a project administrator about the available correction options.
What Changes When an Issue Becomes a Subtask?
A subtask is a child issue connected to a parent, rather than a standalone issue at the same hierarchy level. That relationship helps teams break a larger outcome into pieces with their own owners and progress.
For example, a parent issue called “Prepare the product launch” could contain subtasks for drafting release notes, checking translations, and reviewing the launch page. Each subtask tracks a distinct piece of work while remaining connected to the launch.
Here's why: hierarchy affects more than how an issue looks on screen. It can change which fields are available, how work appears on boards, and how your team reads reports. Check the result in the places where your team plans and reviews work.
Before You Convert: A Quick Readiness Check
First, confirm that the chosen parent is the right one and that the issue really needs to sit beneath it. A subtask is useful for work that contributes to a parent; unrelated work usually belongs as a separate issue.
- Confirm that subtasks are enabled for the project.
- Check that you have permission to edit and convert the issue.
- Choose the parent issue before opening the conversion screen.
- Review required fields for the subtask type.
- Consider how the change may affect boards, reports, and team routines.
Let me explain: a quick check can prevent a common planning problem. If “Update pricing page” is independent of “Prepare the product launch,” placing it underneath that launch may give the team a misleading view of ownership and progress.
What to Check After the Conversion
Start with the issue view. Confirm that the new subtask appears beneath the intended parent and that the summary, description, assignee, priority, and required fields look right.
Then look at the team’s usual planning views. For example, open the relevant board or backlog and see whether the parent and its subtask appear in the expected way. A board’s settings can influence what people see.
You might be wondering: should you also check reports? Yes, if your team uses estimates or issue hierarchy in reporting. Confirm that the converted work is represented as intended, especially if you’re reviewing sprint scope or parent-level progress.
Common Conversion Problems and How to Fix Them
- The conversion option is missing: Check permissions, project configuration, and whether subtasks are enabled. Ask a Jira administrator if the option remains unavailable.
- The parent issue cannot be selected: Confirm that the issue is eligible as a parent and belongs in the expected project context. Try locating it by its issue key.
- A required field blocks the conversion: Fill in the required value or ask an administrator whether the subtask type’s field configuration needs adjustment.
- A field or value changes: Review the conversion prompts carefully, then check the issue after conversion. Field availability can differ between issue types.
- The issue appears differently on a board: Review the board’s filters and display settings. The issue may have converted correctly while the board presents subtasks differently.
But here's the truth: not every unexpected result calls for repeating the conversion. Check the issue history and configuration first, then choose the safest correction with your project administrator.
ONES.com Solution: Project Work and Knowledge in One Platform

Value Proposition
ONES.com brings project management and knowledge management together in a unified platform, with ONES Project for project work and ONES Wiki for team knowledge. The products are sold separately, so you can choose the capabilities that fit your team.
For teams assessing how they manage issue hierarchies and related project information, ONES Project offers Jira-compatible workflows and project management features. It may be worth evaluating when you want a Jira alternative with deployment choices that include on-premise and air-gapped environments.
Core Capabilities
- Jira workflow expectations → Jira-compatible workflows → Teams can work with familiar process patterns while evaluating a different project management platform.
- Scattered progress visibility → Built-in reporting → Project teams can review progress through reports without relying on a separate reporting add-on.
- Rigid issue processes → Custom workflows and fields → Administrators can adapt issue handling to fit a team’s process and information needs.
- Unclear sprint execution → Sprint management → Teams can plan sprint work and monitor the items they have committed to completing.
- Repeated manual actions → Automation → Teams can reduce routine steps by automating supported workflow actions.
- Plugin-heavy setups → Native feature coverage → Built-in capabilities can reduce reliance on additional plugins for supported needs.
- Restricted hosting requirements → Cloud, on-premise, private cloud, and air-gapped deployments → Organizations can assess a deployment model that fits their operating environment.
- Concern about self-hosted capability gaps → Feature parity between cloud and self-hosted versions → Teams can evaluate deployment needs without assuming that self-hosting means fewer features.
- Small teams evaluating the platform → Free plan for up to 30 seats → A team can explore the platform within the plan’s seat limit.
Application Scenarios
A team reviewing Jira alternatives: A project manager can compare familiar workflows, sprint planning, reporting, and automation with the team’s current process. That makes it easier to identify which capabilities are essential and where configuration may need to change.
An organization with restricted network requirements: An administrator can evaluate ONES Project’s on-premise or air-gapped deployment options alongside workflow, reporting, and team access requirements. The review should include how the selected environment supports day-to-day project work.
A team connecting project work with internal guidance: A group can use ONES Project for tracking work and consider ONES Wiki separately for knowledge management. For example, project tasks can be coordinated alongside team guidance for sprint routines or release practices.
Common Challenges When Managing Subtasks
- Creating subtasks without clear ownership: Assign each piece of work to someone responsible, and make the summary specific. “Check translations” is clearer than “Review launch.”
- Choosing a parent that does not match the work: Ask whether the subtask contributes directly to the parent’s outcome. If not, keep it as a separate issue or choose a more suitable parent.
- Overloading the parent with tiny tasks: Split work when separate tracking helps with ownership or progress. Keep minor actions together when individual tracking would add unnecessary overhead.
- Assuming every field will carry over unchanged: Compare the issue before and after conversion, paying attention to required fields and issue-type-specific settings.
- Missing the effect on team views: Check the board, backlog, and reports your team uses. Explain the hierarchy change so teammates understand where to find the work.
Frequently Asked Questions
Can I convert any Jira issue into a subtask?
Not always. The issue must be eligible for conversion, the project must support subtasks, and you need the required permissions. Jira may also limit which issue types can act as subtasks. If the conversion option is missing, check the project configuration and ask a Jira administrator to review the issue type and permission settings.
Will converting an issue delete its comments or attachments?
Conversion behavior can depend on your Jira version and configuration, so check the issue afterward rather than assuming every detail remains unchanged. Review comments, attachments, links, estimates, and the issue history. If an important detail is missing or appears differently, consult your administrator before making further changes.
Can I change the parent after converting an issue?
Often, a subtask can be moved or reassigned to another eligible parent, but the available options depend on your Jira setup and permissions. Open the subtask’s actions or editing options and check for a parent change. Before confirming, make sure the new parent represents the work the subtask supports.
Why can’t I see “Convert to sub-task” in Jira?
The option may be unavailable because subtasks are disabled, your account lacks permission, or the issue type cannot be converted in the current configuration. Jira’s interface can also vary by version. Check the project’s subtask settings and issue type configuration, or ask a project administrator to investigate.
Should I convert a task or create a new subtask instead?
Convert an existing issue when it already represents the work and should become part of a parent’s hierarchy. Create a new subtask when the work has not been tracked yet. Before deciding, check whether the current issue contains useful comments, estimates, or links that your team needs to keep connected.
Conclusion
Converting a Jira issue into a subtask comes down to five checks: confirm eligibility, open the conversion action, select the right parent, review fields, and verify the result. That simple sequence helps keep work organized without losing sight of the details.
When the hierarchy is unclear, your backlog and reports can become harder to trust. Take a moment to confirm the parent and inspect the converted issue, then check your team’s planning views. If Jira’s setup does not match the way your team works, review the configuration or explore whether another project management approach fits better.