How to Delete a Subtask in Jira: 5 Clear Steps to Follow
Need to remove an obsolete subtask without losing useful history? Learn how to delete a subtask in Jira in 5 clear steps. Read now to explore safer options.
Deleting a Jira subtask takes only a few clicks, but the wrong deletion can erase useful work history and disrupt a parent issue’s workflow. The challenge is that Jira’s menus can vary, and the delete option may be hidden when your account lacks permission.
Before you confirm, check that the subtask is truly obsolete and that nobody needs its comments, attachments, or history. But here’s the truth: deleting an issue is different from closing it. Follow these five steps to remove the right subtask, check the result, and choose a safer option when you need to preserve its history.
How to delete a subtask in Jira in 5 steps
To delete a Jira subtask, open it, select Delete from its More menu, and confirm the action. You’ll need the project permission to delete issues. Check the subtask first: deletion can remove its history and is usually difficult to reverse through Jira’s normal interface.
-

1. Open the parent issue and find the subtask
Go to the Jira project and open the parent issue. Find the subtask in its child issues or subtasks panel, then open the subtask itself.
Check the issue key and summary before proceeding. For example, if the parent is PAY-240, make sure you opened the obsolete subtask, such as PAY-241, rather than another child task.
-
2. Check whether deletion is the right choice
Review the subtask’s comments, attachments, assignee, status, and work history. If the task has useful context or was completed, consider keeping it and changing its status instead.
Deleting removes the issue rather than marking it as finished. If your team needs an audit trail, ask the issue owner before you continue.
-
3. Open the issue actions menu
On the subtask’s issue screen, open the More menu, often shown as three dots. Jira’s layout can differ between projects and interface versions, so the menu may appear in a different spot.
Look for Delete. If it isn’t available, you may lack the Delete Issues permission, or your project configuration may limit the action.
-
4. Select Delete and review the confirmation
Choose Delete and read Jira’s confirmation prompt carefully. Confirm that the issue key and summary match the subtask you intend to remove.
Jira may warn you that deletion cannot be undone through the usual issue screen. If you’re unsure, cancel and ask a project administrator or issue owner before making the change.
-
5. Confirm the deletion and check the parent
Confirm the action, then return to the parent issue. Check that the deleted subtask no longer appears in its child issues or subtasks panel.
If the parent’s progress or displayed details look unexpected, review its remaining subtasks and current status. This quick check helps catch mistakes while you still have the issue key and project context at hand.
What to check before removing a Jira subtask
Think of deletion as removing a piece of project history, not tidying a list. The subtask may contain decisions, test results, or discussion that another teammate will need later.
For example, a subtask marked “Duplicate payment retry test” might look redundant, but its comments could explain why a release was delayed. Ask whether the information matters before removing the issue.
- Confirm the issue key and summary.
- Check comments, attachments, and work history for useful details.
- Ask the assignee or parent issue owner if the task is still active.
- Consider whether your team needs a record of the work.
Here’s why: deleting can remove the context that helps people understand what happened. If the issue is simply finished, changing its status may be enough.
Why the Delete option may be missing
The most common reason is permissions. Jira project permissions determine who can delete issues, so being able to edit or assign a subtask does not necessarily mean you can delete it.
Check with a project administrator if you can’t see Delete. They can review your project role and permission scheme, then decide whether you should receive access or whether an administrator should handle the deletion.
The issue screen can also differ by Jira project type and interface. If you see an actions menu but no delete command, verify that you opened the subtask itself, not only the parent issue.
Delete, close, or move a subtask?
Choose the action that matches what you need to happen. Deletion removes the issue; closing or resolving it keeps the task visible in the project’s history.
| Action | When it fits | What to expect |
| Delete | The subtask was created by mistake or should no longer exist. | The issue is removed, and its history may be difficult to recover. |
| Close or resolve | The work is finished, cancelled, or no longer active. | The issue remains available as part of the project’s history. |
| Move or convert | The work still matters but belongs in another place or issue type. | The issue can remain trackable while its organization changes, if your Jira setup supports it. |
You might be wondering: what if the subtask is a duplicate? If it contains no useful information and your team agrees, deletion can make sense. If it explains a decision, closing it and noting the reason may be safer.
What happens after you delete a subtask?
The subtask will no longer appear as an active child issue under its parent. Its comments, status, and other issue details may no longer be available through the normal Jira interface.
Deleting a subtask does not automatically mean the parent issue is complete. Check the parent’s remaining work and workflow status; a team may need to update either one manually.
If you delete the wrong issue, contact a Jira administrator promptly. Recovery options depend on your Jira environment and available backups, so don’t assume you can restore the issue yourself.
Managing project work with ONES.com

Value proposition
ONES.com brings project management and knowledge management together in one platform. ONES Project is a Jira alternative for managing tasks and workflows, while ONES Wiki supports team knowledge management as a Confluence alternative; the products are sold separately.
For teams that want to manage issue lifecycles consistently, ONES Project includes Jira-compatible workflows, sprint management, automation, and built-in reporting. Teams can choose cloud or self-hosted deployment, including on-premise, private cloud, and air-gapped options.
Core capabilities
- Issue removal needs clear control: ONES Project supports custom workflows and fields, helping teams define how tasks move through review, completion, or cancellation.
- Teams need visibility into active work: Built-in reporting helps project leads review progress and identify unfinished items before they make changes.
- Repeated task handling takes time: Automation can handle routine workflow actions, reducing manual updates for common project processes.
- Sprint work needs coordination: Sprint management gives teams a way to organize work and monitor progress through a development cycle.
- Jira workflows are familiar to many teams: Jira-compatible workflows can make it easier to carry over established practices when evaluating a Jira alternative.
- Plugin reliance can add overhead: Native capabilities can reduce the need for plugins to support common project management needs.
- Some teams cannot use public cloud: ONES Project is available in cloud, on-premise, private cloud, and air-gapped deployments.
- Deployment changes can raise feature concerns: The cloud and self-hosted versions have full feature parity, so deployment choice does not require giving up feature access.
Application scenarios
Software team reviewing obsolete work: A team can use a workflow that sends cancelled tasks through a review step before deletion. The project lead can check whether a task has useful comments or active dependencies first.
Organization with restricted network access: A team that needs an air-gapped environment can use a self-hosted deployment while still managing issues, sprints, and workflows. A shared process helps teammates distinguish cancelled work from work that should be deleted.
ONES.com is powered by ONES Assistant, an AI feature. You can consider the platform’s project and knowledge management capabilities separately when comparing options; the best fit depends on your team’s workflow and deployment needs.
Common challenges when deleting subtasks
The subtask has useful comments or attachments
Problem: The task looks unnecessary, but it contains an explanation or attachment that may matter later.
Solution: Ask the issue owner whether the context should be retained. If it should, close or resolve the subtask rather than deleting it.
You can’t find the Delete command
Problem: The issue actions menu does not show a delete option.
Solution: Confirm that you opened the subtask itself. If the option is still missing, contact a project administrator to check your delete permission.
You are unsure which subtask is safe to remove
Problem: Similar summaries make it easy to select the wrong issue.
Solution: Match the issue key, summary, and parent issue before confirming. If anything is unclear, cancel and check with the assignee.
The parent still appears incomplete
Problem: Removing a subtask does not automatically change the parent’s status or complete its remaining work.
Solution: Review the parent issue after deletion. Update its workflow status only when the remaining work and your team’s process support that change.
FAQs about deleting Jira subtasks
Can I delete a Jira subtask without deleting its parent?
Yes. Open the subtask itself and use its issue actions menu to delete that issue. The parent issue remains in Jira, although its list of subtasks will no longer include the deleted task. Before confirming, check the issue key and parent relationship so you don’t accidentally remove the wrong issue.
Why can’t I delete a subtask in Jira?
Your account may not have the project’s Delete Issues permission. The delete command may also be absent if you opened the parent rather than the subtask, or if the interface places actions elsewhere. Ask a project administrator to check your permissions and confirm the project’s setup.
Can I recover a deleted Jira subtask?
Jira’s normal issue interface may not provide a way to restore a deleted subtask. Recovery depends on your environment and the backups or administrative options available to your organization. If you deleted an issue by mistake, contact a Jira administrator promptly and share its issue key and project details.
Should I delete a completed subtask?
Usually, keep a completed task and update its status. That preserves a visible history of the work and makes it easier to understand the parent issue later. Delete a completed subtask only when your team has a clear reason to remove it and does not need its comments, attachments, or history.
Conclusion
To delete a Jira subtask, open the correct child issue, check its history, choose Delete from the issue actions menu, confirm, and review the parent afterward. If the command is missing, ask a project administrator to check your permissions.
Most importantly, decide whether the task should disappear or simply be marked finished. A quick check before deletion can prevent lost context and avoid unnecessary recovery work. When a subtask is obsolete, these steps help you remove it with care.