How to Delete a Subtask in Jira: Step-by-Step Guide [2026]
Worried about deleting the wrong Jira subtask? Learn how to delete a subtask in Jira safely, check permissions, and confirm the right issue. Read now.
Deleting the wrong Jira subtask can erase useful work details, comments, and attachments. If you only need to stop the work, deletion may also be more permanent than necessary.
To delete a subtask in Jira, open it, select the more actions menu, choose Delete, and confirm. You’ll need the right permission, and you should check the subtask’s details before confirming.
But here’s the truth: Jira’s menus can look different across layouts, and deleting an issue is not the same as closing it. Here’s how to find the right action, confirm the correct subtask, and choose a safer option when you need to keep its history.
How to Delete a Subtask in Jira
Open the subtask you want to remove, use its more actions menu to select Delete, and confirm the prompt. These steps apply to Jira Cloud and are similar in many Jira Data Center versions, although menu placement can vary.
- Open the parent issue. Go to the Jira project and open the task, story, or bug that contains the subtask. You can also locate the subtask through Jira search or a board, then open its issue view.
- Check the subtask details. Confirm the summary, issue key, parent, and status. If there is more than one similarly named subtask, compare their issue keys before proceeding.
- Open the subtask itself. Select the subtask so its individual issue view appears. Make sure you are not viewing the parent issue; deleting the parent can affect more work than intended.
- Find the more actions menu. Look for the ellipsis or a menu labeled More near the issue’s actions. In some Jira layouts, the menu is near the top of the issue view.
- Choose Delete. Select Delete from the menu. If the option is missing or unavailable, your account may not have the necessary project permission.
- Review and confirm. Read Jira’s confirmation prompt, then confirm only if you are sure. If Jira displays a warning about related information, stop and check with your project administrator before continuing.
- Verify the result. Return to the parent issue and check its subtask list. The deleted subtask should no longer appear there.
Here’s why the confirmation step matters: deleting removes the subtask from the active Jira project. It isn’t the same as marking the work complete, and restoring it may require administrator help.

Before You Delete: Check Permissions and Impact
Jira projects typically control deletion through the Delete Issues permission. If you cannot see the Delete action, ask a project administrator to check your access rather than looking for a workaround.
For example, a team member may be able to edit a subtask’s summary and status but still lack permission to delete it. That separation helps teams prevent accidental removal while allowing routine updates.
What deletion can affect
Deleting an issue may remove its comments, attachments, and issue history from normal project views. The exact behavior can depend on your Jira configuration, so treat deletion as a permanent action unless your administrator confirms a recovery option.
Before confirming, note the issue key and any details your team may need later. If the subtask records an approval, decision, or completed work, preserve that context in an appropriate place before removing it.
Delete, Close, or Reassign? Choose the Right Action
Deletion is appropriate when a subtask was created by mistake or should no longer exist in the project. If the work happened and you want to retain its history, changing its status is usually a better fit.
Imagine a team creates two subtasks for the same design review. If one is a duplicate with no useful activity, deletion may make sense. If someone has already completed work and added comments, closing it preserves a clearer record.
| Action | Useful when | What to consider |
| Delete | The subtask is an error, duplicate, or no longer needed. | Issue details may no longer be available in the project. |
| Close or resolve | The work is complete, cancelled, or no longer active. | The issue remains available for review, subject to project settings. |
| Reassign | The work still needs to happen but has a different owner. | Update the assignee and clarify ownership or next steps. |
| Edit | The subtask is valid but has an incorrect summary or description. | Correct the details instead of removing the issue. |
You might be wondering: what if the task is no longer relevant, but you need to keep its history? Use your team’s cancellation or closure workflow, if available, and add a brief explanation.
What to Do When Jira Won’t Let You Delete a Subtask
If the Delete option is missing, check your permissions first. Ask a project administrator whether your role has Delete Issues access, and explain why you need to remove the subtask.
If you can select Delete but Jira displays an error, note the message and the issue key. A workflow rule, project configuration, or app may affect the action. An administrator can inspect the project settings and determine what is blocking it.
When you cannot get deletion access
Don’t ask someone to delete the subtask without giving them the reason and issue key. If the team needs a record, request that they close or cancel it instead. This keeps the project tidy without discarding useful context.
For a duplicate, identify which subtask should remain and check whether either has comments or work recorded. That small review can prevent the team from keeping the wrong copy.
Make Subtask Cleanup Safer for Your Team
A short review habit can reduce accidental deletions. Before removing a subtask, verify its parent, issue key, status, assignee, and activity. If it has meaningful history, consider closure instead.
- Confirm the exact subtask and parent issue.
- Check for comments, attachments, or completed work that the team may need.
- Choose deletion only when the issue should no longer remain in the project.
- Ask an administrator about permissions or recovery before making a risky change.
- Tell affected teammates when the subtask is part of active work.
For example, a team cleaning up a sprint board might review duplicate subtasks during planning. They can keep the active issue, close the completed one, and delete only the accidental copy after checking its activity.
Jira Subtask Management with ONES.com
ONES.com brings project management and knowledge management together in one platform. Teams comparing Jira alternatives can use ONES Project for project work and ONES Wiki for team knowledge; the products are sold separately.

For teams that need a Jira alternative, ONES Project supports familiar Jira-compatible workflows, custom fields, reporting, and sprint management. Its deployment choices include Cloud, On-Premise, Private Cloud, and air-gapped environments.
Core capabilities
- Too many project tools: ONES.com combines project and knowledge management in one platform, helping teams keep planning and team knowledge connected.
- Teams want a Jira alternative: ONES Project offers Jira-compatible workflows, making it easier to map familiar issue processes into a different platform.
- Workflows don’t match team needs: Custom workflows and fields let teams shape how issues move and what details they capture.
- Sprint work needs clearer oversight: Sprint management helps teams organize planned work and review progress during a development cycle.
- Manual updates take time: Automation can handle routine workflow actions, giving teams fewer repetitive steps to manage.
- Progress is difficult to track: Built-in reporting gives teams a way to review project activity without relying on extra reporting add-ons.
- Teams depend on multiple plugins: Native capabilities can reduce plugin needs for common project workflows and reporting.
- Hosting requirements are strict: Cloud and self-hosted deployments, including air-gapped options, give organizations deployment choices. ONES.com states that its cloud and self-hosted versions have full feature parity.
Application scenarios
A software team moving from Jira: The team can map its existing issue types, workflows, and sprint practices into ONES Project, then review how subtasks fit the new process before migrating active work.
An organization with restricted networks: A team that cannot use a public cloud service can evaluate On-Premise, Private Cloud, or air-gapped deployment options against its operational requirements.
A team connecting project work with guidance: Teams using ONES Project alongside ONES Wiki can keep delivery work and internal knowledge within the ONES.com platform, while selecting each product separately.
ONES.com offers a free plan for up to 30 seats. If your team is considering a Jira alternative, compare permissions, deletion behavior, deployment needs, and workflow fit before choosing a platform.
Common Challenges When Removing a Subtask
The Delete option is missing
Problem: You can open and edit the subtask, but the action menu does not offer deletion. Solution: Ask a project administrator to check your Delete Issues permission. If deletion is not appropriate for your role, request closure or another approved action.
You are unsure which subtask is the duplicate
Problem: Two subtasks have similar summaries. Solution: Compare their issue keys, parent, status, assignee, and activity before choosing. Keep the copy with relevant work and comments.
You need to preserve completed work
Problem: The subtask is no longer active, but its work may matter later. Solution: Change its status to a suitable completed or cancelled state instead of deleting it, if your workflow supports that option.
You deleted the wrong issue
Problem: The subtask is gone, and you need it back. Solution: Contact your Jira administrator promptly with the issue key and deletion details. Recovery options depend on your organization’s configuration and backups, so restoration may not be available.
Frequently Asked Questions
Can I delete a subtask without deleting its parent?
Yes. Open the subtask’s own issue view and choose Delete from that issue’s more actions menu. Check the issue key and parent before confirming so you know you are acting on the subtask, not the parent task. Deleting the parent is a separate action and can have a wider effect on related work.
Why can’t I see the Delete option in Jira?
Your account may not have the project’s Delete Issues permission. The Jira layout or project configuration can also affect which actions appear. Ask a project administrator to check your access and confirm whether another rule is preventing deletion. If you only need to stop the work, ask whether closing or cancelling the subtask is more suitable.
Can I recover a deleted Jira subtask?
Recovery depends on your Jira setup and the time elapsed since deletion. Jira may not provide a simple restore action for deleted issues in your project view. Contact your administrator with the issue key and explain what happened. They can check whether your organization has a recovery process, but you should not assume the subtask can be restored.
Should I delete a completed subtask?
Usually, keeping a completed subtask closed or resolved is more useful when it records work the team may need to review. Deletion is a better fit for an accidental issue or an unnecessary duplicate with no valuable activity. Consider your team’s retention and audit practices before removing any completed work.
Conclusion
To remove a Jira subtask, open its individual issue view, choose Delete from the more actions menu, and confirm only after checking the issue key and activity. If the option is unavailable, ask an administrator to review your permissions.
But here’s the truth: deletion can remove context your team may need later. Close, cancel, edit, or reassign the subtask when that better reflects what happened. A quick check before confirming keeps Jira cleaner while reducing the risk of losing useful work history.