Can You Change a Jira Subtask Into a Task? Steps & Tips
Need to turn a Jira subtask into a task? Follow the steps for jira change subtask to task, review hierarchy and fields, and convert it safely. Read now.
Yes—you can convert a Jira subtask into a standard issue and choose Task if that issue type is available in your project. Open the subtask, select More > Convert to issue, follow the prompts, and confirm the change. Menu labels can vary by Jira version and project settings.
But a subtask has a parent relationship, so converting it changes where it sits in your project’s hierarchy. The former parent won’t remain its subtask parent, and some fields may need attention during conversion. Skip that review, and the new issue could have an unexpected status, assignee, or issue type.
Here’s why this matters: a careful conversion keeps work visible without leaving it tied to the wrong parent. I’ll walk you through the steps, explain what to check, and show what to try if the conversion option is missing.
How to Change a Jira Subtask Into a Task
Use Jira’s conversion action to turn the subtask into a standard issue, then choose the Task issue type when prompted. Check the fields and hierarchy before confirming.
- Open the subtask. Find it through its parent issue or Jira search. Confirm you have the right issue by checking its summary and key details.
- Open the issue actions. Select More near the top of the issue, then choose Convert to issue. Depending on your Jira version, the action may appear in a different menu.
- Choose the new issue type. Select Task if it is available. If you want another standard issue type, such as Bug or Story, choose that instead.
- Review the conversion fields. Check the summary, description, assignee, priority, status, and any project-specific fields Jira presents. Update required fields before moving on.
- Check the confirmation screen. Review Jira’s summary of the change, especially the issue type and parent relationship. Confirm only when the details look right.
- Verify the result. Reopen the issue and confirm it appears as a standard issue. If you still need a connection to the former parent, add an appropriate issue link.
But here’s the truth: conversion changes the issue’s place in the hierarchy. A standard task is not a subtask, so it won’t stay underneath the former parent in the same way.

What Changes When You Convert a Subtask
A subtask is a child issue connected to a parent. After conversion, Jira treats it as a standard issue, which can change how the work appears in parent views, boards, and reports.
For example, imagine a subtask called “Write checkout tests” under “Build payment flow.” Once converted, “Write checkout tests” becomes a separate task. You can still connect it to the payment work with an issue link, but that link is different from the subtask relationship.
Check the New Issue’s Place in the Hierarchy
Consider where the converted task should live. If your project supports a suitable parent relationship, such as placing work under an epic, set that relationship after conversion. Otherwise, link it to the former parent so teammates can still find the connection.
Think of the change as moving a work item out of a folder and placing it on its own shelf. The item remains, but its old location no longer organizes it.
What to Check Before Converting
A quick review can prevent avoidable cleanup. Before you start, check whether the task genuinely needs to stand alone or whether the current parent relationship still reflects how the work should be managed.
- Issue type: Confirm that Task is available in the project and suits the work.
- Required fields: Check which fields the destination issue type requires, including any custom fields.
- Status: Verify that the current status makes sense in the standard issue workflow.
- Ownership: Note the current assignee and priority so you can confirm them afterward.
- Parent and links: Decide whether to create a new issue link or assign another supported parent relationship.
For example, a subtask in “To Do” may convert into a task whose workflow uses “Open.” That difference may be expected, but it’s better to notice it before teammates see an unfamiliar status.
Why the Conversion Option Might Be Missing
If you can’t find Convert to issue, first check that you opened the subtask itself rather than its parent. Then inspect the issue actions menu; Jira can place actions differently across versions and project configurations.
Permissions and project settings can also limit available actions. Ask a Jira administrator to check your permissions and whether the relevant issue types and workflows are configured for the project. For example, Task may exist in Jira but still be unavailable for that particular project.
Try an Administrator-Assisted Route
If the conversion action remains unavailable, ask an administrator to review the project’s issue type configuration and workflow. They can help determine whether conversion is supported or whether another approved method fits your setup.
Avoid changing the issue type or hierarchy through an improvised workaround. A quick administrative check is safer than leaving the issue with an invalid status or incomplete required fields.
What to Do After the Conversion
Once the change is complete, open the new task and check its details. Confirm the issue type, status, assignee, priority, and required fields. Then check the board or parent view where the team expects to find the work.
If the task should remain connected to its former parent, add an issue link with a clear relationship, such as “relates to” or another link type your team uses. Add a short comment explaining the conversion when teammates might otherwise wonder why the subtask disappeared.
For example, a team could link “Write checkout tests” to “Build payment flow” and add a note explaining that testing now has its own owner and delivery status. That keeps the relationship visible without presenting the task as a child issue.
ONES.com for Teams Reviewing Their Jira Workflow
ONES.com brings project management and knowledge management together in a unified platform powered by ONES Assistant. ONES Project is a Jira alternative, and ONES Wiki is a Confluence alternative; they are sold separately.

If your team is reviewing how it manages tasks, workflows, and project knowledge, the platform offers another environment to consider. Its free plan supports up to 30 seats, and it offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. The cloud and self-hosted versions have full feature parity.
Core Capabilities
- Project work is scattered across different tools: ONES Project provides project management capabilities in one platform, helping teams keep work organized.
- Teams need familiar Jira patterns: Jira-compatible workflows can make it easier to map established processes into an alternative environment.
- Issue types need to match real work: Custom workflows and fields let teams shape issue handling around their requirements.
- Sprint planning needs structure: Sprint management supports teams planning and tracking iterative work.
- Progress is hard to assess: Built-in reporting gives teams a way to review project activity without relying entirely on added plugins.
- Repeated actions consume time: Automation can handle routine workflow actions and reduce manual follow-up.
- Self-hosting is a requirement: On-Premise, Private Cloud, and Air-gapped deployments give teams deployment choices for their environments.
- Project work and team knowledge are disconnected: ONES Wiki offers a separate knowledge management option alongside ONES Project.
Application Scenarios
A team with complex Jira workflows: A team reviewing a growing collection of workflows and plugins can assess ONES Project as a Jira alternative. It can compare required workflow behavior, reporting, sprint processes, and automation before deciding whether a transition is practical.
A team in a restricted network: An organization with strict hosting requirements can evaluate the Air-gapped or other self-hosted deployments. Full feature parity between cloud and self-hosted versions helps teams assess deployment needs without assuming a reduced feature set.
ONES.com is worth considering when the broader project management setup is under review. For a single subtask conversion, Jira’s built-in action may be all you need.
Common Challenges and Practical Fixes
The Former Parent No Longer Shows the Work
Problem: After conversion, the task no longer appears as a subtask under its former parent. Solution: Add a suitable issue link or assign a supported new parent relationship, then tell the team where to find the task.
Required Fields Prevent Completion
Problem: Jira asks for fields that were not needed for the subtask’s previous issue type. Solution: Complete the required fields shown during conversion. If you’re unsure what a field means, ask the project administrator before confirming.
The Task Has an Unexpected Status
Problem: The destination issue type uses a different workflow, so the converted task may show a status your team didn’t expect. Solution: Review the status during conversion and check the issue afterward. Ask an administrator for help if the required status isn’t available.
Task Is Not an Available Issue Type
Problem: The project doesn’t offer Task as a choice. Solution: Check whether another standard issue type fits. If Task is essential, ask an administrator to review the project’s issue type configuration.
FAQs
Can I convert a Jira subtask directly into a task?
Yes. Open the subtask, choose More > Convert to issue, and select Task if it’s available. Review the fields and confirm the conversion. Jira’s menu labels can vary by version or project setup, and some accounts may not have permission to perform the change. If the action is missing, ask a project administrator to check your access and configuration.
Will the converted task remain under its original parent?
No. Converting a subtask into a standard issue removes the subtask’s parent-child relationship. You can usually preserve a useful connection by adding an issue link, or by assigning a supported parent relationship after conversion. Check your project’s hierarchy rules first, since the available relationships depend on how the project is configured.
Can I change a subtask into a different issue type?
Often, yes. The conversion prompt may let you choose another standard issue type, such as Bug or Story, if that type is available in the project. The destination type can have different required fields and workflow statuses. Review the prompt carefully, then verify the converted issue’s type and status before relying on it in team planning.
What if “Convert to issue” does not appear?
Make sure you opened the subtask itself and checked its issue actions menu. If the action is still missing, your permissions or project configuration may limit conversion. Ask a Jira administrator to check whether your account can perform the action and whether the destination issue type is available. Avoid trying an unapproved workaround that could leave the issue in an inconsistent state.
Conclusion
You can change a Jira subtask into a standard task through More > Convert to issue, provided the action and Task issue type are available in your project. Before confirming, review required fields, status, ownership, and the task’s future relationship to its former parent.
The key point is simple: conversion gives the work a standalone place, but it changes the hierarchy. Check the result afterward, and add an issue link when the former parent relationship still matters. That small review helps your team keep ownership and context clear.