Jira: Convert an Issue to a Subtask in 5 Clear Steps (2026)
Need to turn a Jira issue into a subtask? Learn jira convert to subtask in 5 clear steps without losing useful details. Read now.
Have you ever created a Jira issue that should have been part of a larger task, only to realize it needs to become a subtask? The wrong hierarchy can make ownership unclear, distort sprint planning, and leave related work scattered across your project. Deleting the issue and starting over might seem easier, but that can cost you useful details and disrupt the conversation around the work. Jira can convert an existing issue into a subtask in five steps, as long as the project and parent issue meet a few requirements. But here's the truth: the conversion option may be hidden, or unavailable, depending on your permissions and project setup. Here’s how to check the basics, run the conversion, and fix common snags without losing track of the work.
How to Convert a Jira Issue to a Subtask in 5 Steps
Open the issue you want to change, choose the conversion action, select a parent issue, review the fields, and confirm. The exact menu label can vary slightly by Jira experience, but the overall process is similar.
- Check that the project and issue are eligible.
Confirm that the issue and its intended parent belong to the same Jira project. The project must support subtasks, and you need permission to edit the issue and create or manage subtasks. If the issue already has subtasks, review the hierarchy before continuing; Jira may prevent the conversion until you address them.
- Open the issue you want to convert.
Find the issue in Jira and open its full details page. Check the issue key, summary, and project name before making changes. For example, if APP-248 describes a small task that belongs under a larger feature, open APP-248 rather than the feature itself.
- Choose the conversion action.
Open the issue’s More or More actions menu and select Convert to sub-task or the closest equivalent. Menu wording can differ between Jira Cloud and Data Center, and between interface versions. If you can’t find the action, check the troubleshooting section below before assuming conversion is impossible.
- Select the parent issue and review fields.
Choose the issue that will become the parent, then review any fields Jira asks you to confirm or change. The parent should represent the larger piece of work; the new subtask should describe a smaller, independently trackable action. For example, “Add export button” might sit under “Build report export.”
- Confirm the conversion and verify the result.
Review the parent, issue type, summary, assignee, and other displayed details. Confirm the conversion, then reopen the issue or parent to make sure the hierarchy appears correctly. Check that comments and important fields remain as expected, and tell affected teammates if the change alters their work queue.

What Changes When an Issue Becomes a Subtask?
A subtask sits beneath a parent issue in Jira’s work hierarchy. It helps you track a specific piece of work while keeping it connected to a broader task, story, or other eligible parent. The parent gives the work context; the subtask gives a teammate a focused item to complete.
For example, a team building a checkout page might use “Build checkout page” as the parent. “Add address validation” and “Test payment errors” could become separate subtasks. Each item can have its own assignee and status, while the parent remains the place to see how the larger effort is progressing.
Conversion Is Different from Creating a New Subtask
Creating a new subtask starts with a new Jira issue. Converting an existing issue changes its place in the hierarchy, which can be useful when the work already has a summary, comments, or assignment you want to retain. Still, review the conversion screen carefully, since the issue type and available fields can change during the process.
Before You Convert: Check These Requirements
A quick check can prevent a failed conversion or a confusing hierarchy. First, make sure the intended parent is eligible and in the same project. Then check that the project’s issue type setup allows subtasks and that your Jira role gives you the permissions needed for the change.
Consider whether the issue’s current content still makes sense as a subtask. A broad issue such as “Improve onboarding” may be too large to sit beneath a more specific parent. Something like “Add welcome email to onboarding flow” is easier to understand and assign as a smaller unit of work.
Check the Work Hierarchy, Not Just the Menu
Pick a parent that explains why the subtask exists. If the parent and subtask describe unrelated work, the hierarchy may technically work but still confuse people reviewing the project. A clear parent-child relationship also makes sprint planning and progress checks easier to follow.
It helps to agree on a simple rule with your team: use subtasks for distinct actions that contribute to one parent’s outcome. If a task has its own independent goal, dependencies, or planning cycle, it may be better kept at the same level as other major work items.
Common Problems and How to Fix Them
If Convert to sub-task is missing, start with permissions and project configuration. Your Jira administrator can check whether the project supports subtasks and whether your role can edit the issue. Also confirm you have opened an issue type that can be converted, rather than a project page or a parent with a different hierarchy role.
If Jira rejects the selected parent, check whether it belongs to the same project and can contain subtasks. If the conversion screen flags required fields, complete them before proceeding. A field that was optional on the original issue may be required for its new issue type.
When the Issue Already Has Subtasks
An issue with existing subtasks can complicate conversion because Jira must preserve a valid hierarchy. If Jira blocks the action, review the message it displays and ask your administrator about the project’s available options. You may need to move or resolve the existing subtasks before converting the parent issue.
Don’t create a replacement issue until you understand what will happen to the original discussion and history. If you do need a new subtask, link it to the right parent and clearly indicate how the previous issue relates to the new one.
A Practical Example: Turn a Standalone Task into a Subtask
Imagine a product team has a standalone issue called “Add password reset confirmation.” During planning, the team decides that this work belongs under “Improve account recovery.” The original issue already has an assignee and several comments, so converting it can keep the work’s context together.
The teammate opens the standalone issue, selects the conversion action, chooses “Improve account recovery” as the parent, and checks the fields Jira presents. After confirming, they open the parent and verify that the converted issue appears beneath it. The team can now review account recovery work in one place while still tracking the confirmation task separately.
But here's the truth: a technically successful conversion can still create confusion if nobody knows why the hierarchy changed. Add a brief comment or team update when the move affects sprint plans, ownership, or reporting. That small step can help prevent someone from treating the subtask as new or unrelated work.
Project Management Alternative: ONES.com
ONES.com brings project management and knowledge management together in one platform, with AI features powered by ONES Assistant. ONES Project is a Jira alternative for teams that need issue tracking, sprint planning, and adaptable workflows. ONES Wiki is a Confluence alternative for teams that also need a knowledge base; the two products are sold separately.

Core Capabilities
- Need familiar Jira-style work tracking? ONES Project supports Jira-compatible workflows, helping teams carry familiar ways of organizing work into a new project environment.
- Need to adjust how work moves? Custom workflows let teams shape issue states and transitions around their process, so a task can follow the right path from request to completion.
- Need project-specific issue details? Custom fields let teams capture information relevant to their work, helping teammates understand an issue without relying on extra workarounds.
- Need to plan iterative delivery? Sprint management supports teams organizing work into time-boxed cycles and reviewing progress as they go.
- Need visibility into project progress? Built-in reporting helps teams review delivery and workload without assembling every view through separate add-ons.
- Need repetitive actions handled consistently? Automation can reduce manual steps for routine project workflows, freeing teammates to focus on the work itself.
- Need fewer external plugins? Native capabilities can cover common workflow and reporting needs, which may reduce plugin dependence and the extra administration it brings.
- Need a deployment that fits security requirements? ONES.com supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Its self-hosted versions have full feature parity with the cloud version.
Where It May Fit
A Jira team with customized issue flows can evaluate ONES Project when it wants Jira-compatible workflows alongside built-in reporting and customization. A team with restricted network requirements can assess its On-Premise, Private Cloud, or Air-gapped deployment options.
Teams that manage projects alongside internal knowledge may also consider ONES Wiki as a separate product. For example, a product group could track delivery in ONES Project and maintain team guidance in ONES Wiki, without treating the two as a single purchase.
Common Challenges When Managing Subtasks
- Problem: The parent is too vague. A subtask may be hard to prioritize if its parent gives no context. Choose a parent that describes the intended outcome, and make the subtask summary specific enough to stand on its own.
- Problem: The subtask is too large. If one item includes several distinct actions, ownership and progress can become difficult to judge. Break it into smaller subtasks when each action needs separate tracking, or keep it as a regular issue if it has an independent goal.
- Problem: Teammates miss the hierarchy change. Someone may still look for the issue in its old location or misunderstand a changed sprint plan. Leave a short comment or notify the people whose work is affected.
- Problem: The conversion option is unavailable. Permissions, project configuration, issue type, or an existing hierarchy may be responsible. Check the issue details and ask a Jira administrator to review the project setup if the cause isn’t clear.
FAQs About Jira Subtask Conversion
Can I convert any Jira issue into a subtask?
Not necessarily. The project must support subtasks, and the chosen parent must be eligible to contain them. Your permissions and the issue’s current hierarchy may also affect whether Jira offers the conversion action. If the option is missing, check the project setup and ask a Jira administrator to review your access before changing the issue manually.
Will converting an issue delete its comments?
The conversion changes the issue’s type and hierarchy; it doesn’t mean you should assume every detail will remain unchanged. Review the conversion screen and check the issue afterward, including its comments and fields. If a particular discussion or detail is important to your team, verify that it remains visible before relying on the converted issue for ongoing work.
Can a subtask have its own subtasks?
Jira’s supported hierarchy depends on the product configuration and issue types available to your project. In many standard setups, subtasks are the lowest level and cannot contain another layer of subtasks. Check your Jira project’s hierarchy rules before designing a multi-level structure, and use linked issues or another supported issue type when you need to show related work.
What should I do if the conversion action does not appear?
Confirm that you opened the issue itself and that it belongs to a project configured for subtasks. Then check your edit permissions and whether the issue’s current hierarchy allows conversion. Menu labels can vary across Jira experiences, so inspect the full actions menu. If the action still isn’t available, ask your Jira administrator to check the project settings and your access.
Conclusion
You can convert a Jira issue into a subtask by opening it, choosing the conversion action, selecting a suitable parent, reviewing the fields, and confirming the change. First check project support, permissions, and the existing hierarchy. Then verify the result and tell teammates if the change affects their plans.
That small workflow can keep related work connected without discarding useful context. When Jira’s hierarchy or project setup doesn’t fit the way your team works, review your configuration or explore a Jira alternative such as ONES Project. A clear parent and a focused subtask make the work easier to assign, follow, and complete.