How to Delete a Subtask in Jira: A Step-by-Step Guide (2026)
Need to remove a mistaken Jira subtask? Learn how to delete subtask in Jira, check permissions, and protect work history. Read now to act safely.
Deleting a Jira subtask can look like a quick cleanup, especially when it was created by mistake or no longer belongs in the plan. But one wrong click can remove work history your team still needs, and you may not be able to restore the issue easily.
That makes it worth checking the subtask, its parent, and your project permissions before you act. You may only need to close or reassign it instead.
Here’s how to delete a subtask in Jira, what to verify first, and what to try if the Delete option is missing. I’ll also explain when another action is safer, so you can clean up your project without surprising your team.
How to Delete a Subtask in Jira
Open the subtask, choose Delete from its issue actions, and confirm the deletion. Before you do, check that you have the right issue and permission to delete issues in the project.
-

1. Open the subtask you want to remove
Go to the parent issue and find the subtask in its subtask list, or search for the subtask by its issue key. Open the subtask itself, rather than the parent issue.
Check the issue key, summary, and parent link. For example, if the parent is “Prepare product launch” and the subtask is “Draft launch email,” make sure you have the email task open.
-
2. Open the issue actions menu
In the subtask view, select the More or three-dot menu. The menu location can vary with Jira’s interface and project configuration.
Look for Delete. If the option is missing, don’t assume the issue is locked; your account may lack the required permission, or your project may use a different workflow.
-
3. Confirm that deletion is the right action
Before continuing, check whether the subtask has comments, work logs, attachments, links, or a record of completed work that your team needs. Consider whether closing or reassigning the issue would preserve useful context.
Jira may show a confirmation prompt. Read it carefully, especially if it warns about related work or other issues affected by the action.
-
4. Confirm the deletion
Select Delete in the confirmation prompt if you’re sure. Jira should return you to another view or show a confirmation that the issue was removed.
Check the parent issue afterward. Confirm the subtask no longer appears and that the remaining subtasks and parent issue still look correct.
-
5. Tell your team what changed
If teammates were assigned work or tracking progress on the subtask, let them know it was deleted. Share the reason and point them to a replacement task if one exists.
This small follow-up prevents someone from searching for a task that is no longer available or repeating work that has already been reassigned.
What to Check Before Removing a Subtask
Start with the issue’s status and activity. A task with no work recorded may be a straightforward cleanup; a completed subtask with comments or logged time may contain context your team will want later.
Next, check whether the subtask is linked to another issue or mentioned in a release plan. For example, deleting a testing task could leave a bug report without a clear explanation of which test uncovered it.
But here's the truth: deletion is not the only way to remove a task from someone’s active workload. If the task is no longer relevant but its history matters, closing it with a clear resolution can preserve a useful record.
Delete, Close, or Reassign: Which Action Fits?
Use deletion when the issue was created by mistake, is a duplicate, or has no continuing value. Use closure when the team needs a record showing that the work was considered and intentionally stopped.
Reassignment works when the task still needs attention but the current owner cannot complete it. For example, a subtask assigned to a departing teammate can move to another owner without losing its comments or progress.
| Action | Best fit | What to consider |
| Delete | Accidental, duplicate, or unnecessary issue | Check for useful history and confirm the exact issue before proceeding. |
| Close | Work that was reviewed but will not continue | Add a resolution or comment that explains why it stopped. |
| Reassign | Valid work with a different owner | Confirm the new assignee understands the task and next step. |
Here's why the distinction matters: deletion removes the issue from normal project work, while closure and reassignment keep a visible trail. Choose the action that matches what your team may need to understand later.
Why the Delete Option May Be Missing
The most common reason is permissions. Jira projects can restrict who may delete issues, so an account that can edit or assign a subtask may still be unable to delete it.
Ask a Jira administrator or project administrator to check your project permissions. Include the subtask key, project name, and the action you need; that gives them enough detail to investigate without guessing.
You might be wondering: could the workflow be the cause? It can affect which actions appear, and Jira’s menus can differ across projects and interface versions. If your permissions look correct, ask an administrator to review the project’s configuration.
How to Reduce Accidental Subtask Deletion
Make a quick verification habit part of cleanup: open the issue, read its key and summary, confirm its parent, and scan its activity. This takes only a few seconds and helps prevent deleting a similarly named task.
For example, a project may have “Update help page” subtasks under both a launch issue and a maintenance issue. Checking the parent link can reveal that the task you opened belongs to active work.
The best part? A short team rule can make cleanup more consistent. You might ask teammates to close completed work, add a reason when stopping an active task, and reserve deletion for mistakes or duplicates.
Subtask Management with ONES.com
ONES.com combines project management and knowledge management in one platform. ONES Project is its project management product and a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

For teams that regularly create, update, or retire subtasks, clear workflows can make the decision easier. ONES Project supports Jira-compatible workflows, custom fields, sprint management, automation, and built-in reporting. The platform is available in Cloud, On-Premise, Private Cloud, and air-gapped deployments, with feature parity between cloud and self-hosted versions.
Core capabilities for managing project work
- Unclear task ownership → Custom workflows and fields → Capture ownership and issue details in a way that fits your team’s process.
- Inconsistent status changes → Jira-compatible workflows → Keep familiar issue transitions while adapting the workflow to your project.
- Subtasks falling through the cracks → Sprint management → Organize work into sprints and review the tasks that need attention.
- Manual repeat actions → Automation → Reduce routine updates by automating appropriate workflow actions.
- Limited progress visibility → Built-in reporting → Review project progress without relying on a collection of separate reporting plugins.
- Plugin-heavy project setup → Native project capabilities → Handle common planning and tracking needs within ONES Project, which can reduce reliance on add-ons.
- Restrictions on where project work runs → Four deployment options → Choose Cloud, On-Premise, Private Cloud, or air-gapped deployment to match operational requirements.
- Need to retain control of the environment → Self-hosted deployment options → Run the platform on-premise or in a private cloud while retaining feature parity with the cloud version.
Application scenarios
Jira migration: A project team that knows Jira issue workflows can use Jira-compatible workflows in ONES Project while considering how custom fields, sprints, and reporting should map to its process.
Restricted environments: A team with on-premise or air-gapped requirements can evaluate the matching deployment option and manage project work within that environment.
Fewer disconnected tools: A team that wants project management and knowledge management from the same provider can evaluate ONES Project and ONES Wiki as separately sold products.
Common Challenges When Deleting a Subtask
- You can’t see Delete. Your account may not have permission. Ask a project administrator to review the project’s delete-issue permission and explain why you need the change.
- You’re unsure whether the task is a duplicate. Compare its issue key, parent, summary, and activity with the suspected duplicate. If the distinction remains unclear, check with the assignee before deleting either one.
- The task has completed work attached to it. Deletion may remove access to context your team expects to retain. Consider closing the task and adding a concise explanation instead.
- You deleted the wrong issue. Contact your Jira administrator promptly. Recovery options can depend on the project setup and available backups, so avoid promising that the issue can be restored.
FAQs About Jira Subtasks
Can I delete a subtask without deleting its parent issue?
Yes. Open the subtask itself and use its issue actions menu to delete that issue. Then check the parent issue to confirm it remains and the subtask no longer appears. Take care not to open the parent issue’s action menu by mistake, particularly when both issues have similar summaries.
Why can I edit a subtask but not delete it?
Jira can assign different permissions to editing and deleting issues. Your role may allow changes to the summary or assignee while preventing deletion. Ask a project administrator to check the permission configuration for your account and the relevant project. The available actions can also differ across project configurations.
Can I recover a Jira subtask after deleting it?
Recovery is not guaranteed. It depends on your Jira environment, project setup, and whether an administrator has a suitable backup or recovery process. If you deleted an issue accidentally, contact your Jira administrator as soon as possible and provide its issue key, project, and approximate deletion time.
Should I delete a completed subtask?
Usually, keep completed work visible if its history helps explain the project’s progress. Closing or resolving the subtask preserves a clearer record of what was done. Delete it when it was created by mistake, duplicates another issue, or has no continuing value to your team.
Conclusion
To delete a subtask in Jira, open the subtask, use its issue actions menu, select Delete, and confirm only after checking the issue and its history. If you can’t see the option, ask an administrator to review your permissions.
Use deletion for mistakes or unnecessary issues; close or reassign work when your team needs its history. A quick check of the issue key, parent, and activity can prevent an avoidable cleanup problem.