How to Delete a Subtask in Jira: Follow These 6 Simple Steps
Need to remove an outdated task? Learn how to delete a subtask in Jira in six simple steps and handle a missing Delete option. Read now.
Deleting a Jira subtask takes only a few clicks, but choosing the wrong issue can remove work your team still needs. That can leave a parent task confusing, erase useful discussion, and force teammates to recreate details.
Maybe the subtask is duplicated, created under the wrong parent, or simply no longer relevant. But here's the truth: deletion is straightforward when you know which menu to open and what the confirmation means.
I’ll walk you through six steps, show you what to check first, and explain what to do if the Delete option is missing. You’ll also learn safer options for work that should stay visible and practical ways to keep project workflows organized.
How to delete a subtask in Jira in 6 steps
Open the subtask itself, choose More actions, select Delete, and confirm. These six steps walk you through the process in Jira Cloud; labels and menu placement can vary slightly by Jira version.
- Open the parent issue. Go to the Jira project and find the parent task, story, or bug that contains the subtask. You can use search or a board if that’s quicker.
- Find the subtask. Look for the Subtasks section on the parent issue. Check the subtask’s summary and key carefully so you don’t select a similar item by mistake.
- Open the subtask. Select its summary or issue key to view the full issue. Confirm that the parent and details match the subtask you intend to remove.
- Open the action menu. Select the More actions menu, often shown as three dots (•••), near the issue’s controls.
- Choose Delete. Select Delete from the menu. If you don’t see it, you may not have permission to delete issues in that project.
- Review and confirm. Read the confirmation prompt, then confirm the deletion if you’re sure. Return to the parent issue and check that the subtask no longer appears.
The key safeguard is checking the subtask’s summary and parent before confirming. If the issue contains work you may need later, consider closing it or changing its status instead.

Check these details before you remove a subtask
Deletion removes the subtask as an issue, so pause before confirming. Check its status, comments, attachments, and any links or references your team may need.
For example, a subtask might look redundant but contain a useful testing note. If that note matters to a release decision, copy the relevant details into the parent issue or another appropriate place before deleting.
Also check whether the subtask is assigned, included in active work, or mentioned in a team conversation. A quick check can prevent confusion when someone later searches for an issue that no longer exists.
What happens after a Jira subtask is deleted?
The subtask disappears from the parent issue’s subtask list because the issue itself has been deleted. The parent issue remains, along with its other subtasks and its own status.
For instance, if a parent task has three subtasks and you delete one, the other two remain attached to the parent. The deleted subtask’s summary and issue key may still appear in old conversations or external notes, which can confuse teammates.
Deletion is different from closing a subtask. Closing it keeps the issue available for reference while showing that the work is finished. If your team needs an audit trail or may revisit the work, check your project’s retention and recovery options before deleting.
If the Delete option is missing
The most common reason is permissions. Jira project permissions control who can delete issues, so a project administrator may need to grant the required access or delete the subtask for you.
First, confirm you opened the subtask rather than the parent issue. Then check whether your account has the relevant project permission. If both look correct, your Jira administrator can review project configuration and any interface differences in your Jira version.
A missing option doesn’t mean the subtask is stuck. If you can’t delete it, ask a project administrator, or use an approved status change to make clear that the work is no longer active.
Choose deletion only when it fits the situation
Deletion makes sense for a duplicate, an accidental test issue, or a subtask created in error. For work that is complete or no longer planned, keeping the issue and changing its status may preserve useful context.
For example, say a developer created two subtasks for the same code review. If one has no useful activity, deleting the duplicate may be sensible. If both contain team decisions, close one and explain the relationship in the other.
When your team handles similar cleanup regularly, agree on a simple rule: delete accidental issues, close completed work, and preserve issues that may be needed for later reference. That consistency helps prevent different teammates from making conflicting choices.
Project workflow management with ONES.com
If you’re reviewing how your team manages tasks beyond a single Jira issue, ONES.com brings project management and knowledge management together in one platform. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge base product. They’re sold separately.

For teams comparing project workflows, ONES Project offers Jira-compatible workflows, reporting, custom fields, sprint management, and automation. Its deployment choices include cloud and self-hosted options, including on-premise and air-gapped environments.
Core capabilities
- Work is scattered across disconnected systems: ONES.com combines project management and knowledge management in one platform, while ONES Project and ONES Wiki remain separately available products. This can help teams keep work tracking and team knowledge within a consistent environment.
- Moving away from familiar Jira processes feels disruptive: ONES Project supports Jira-compatible workflows. Teams can carry familiar ways of organizing and progressing work into a Jira alternative.
- Standard issue fields don’t fit the team’s work: Custom fields let teams capture relevant details for tasks and issues. People can see the information needed to move work forward.
- Reports require too much manual effort: Built-in reporting gives teams views of project progress and workload. That makes it easier to spot issues needing attention.
- Sprint work needs clearer coordination: Sprint management supports planning and tracking work across a sprint. Teams can keep planned tasks visible as delivery progresses.
- Repeated handoffs create extra steps: Automation can handle selected routine actions. That reduces manual coordination for workflows the team configures.
- Third-party add-ons increase maintenance: Native capabilities across project management workflows can reduce reliance on plugins for common needs. Fewer separate add-ons can mean less configuration to maintain.
- Hosting requirements restrict cloud-only choices: ONES.com is available in Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Its self-hosted version has full feature parity with cloud, giving teams options for restricted environments.
Where it can fit
A product team moving from Jira could use ONES Project to manage custom workflows, sprints, and reporting while assessing a Jira alternative. The team can decide how to handle duplicated or obsolete issues through its own project rules.
A company operating in a restricted network could consider an air-gapped deployment for project management. Teams that also want a dedicated knowledge base can evaluate ONES Wiki separately from ONES Project.
Common challenges when deleting a subtask
You’re unsure whether it’s the right subtask
Problem: Similar summaries can make two issues easy to confuse. Solution: Open the subtask and verify its issue key, parent, summary, and activity before choosing Delete.
The issue contains details worth keeping
Problem: Comments or attachments may hold context needed by the team. Solution: Review the issue first, preserve relevant details in an appropriate place, or close the subtask instead.
You can’t find the Delete action
Problem: Your account may not have permission to delete project issues, or the menu may differ in your Jira version. Solution: Confirm you’re viewing the subtask, then ask a project administrator to check access.
The parent issue still shows a reference elsewhere
Problem: Old messages or team notes may still mention the deleted issue key. Solution: Update important references where practical and let affected teammates know the subtask was removed.
FAQs about deleting Jira subtasks
Can I delete a subtask without deleting its parent issue?
Yes. A subtask is a separate issue linked to its parent. Deleting the subtask removes that subtask, while the parent and its other subtasks remain. Before confirming, check that you opened the subtask itself and not the parent issue. If you only want to mark the work complete, changing the subtask’s status may be a better fit.
Why can’t I delete a subtask in Jira?
Your Jira account may not have permission to delete issues in the project. The option may also appear in a different place depending on your Jira version or interface. Confirm you’re viewing the subtask, then ask a project administrator to review your project permissions if Delete is still unavailable.
Can I recover a Jira subtask after deleting it?
Don’t assume you can restore a deleted issue. Recovery options depend on your Jira setup and any administrative backups or retention processes. If the subtask contains information your team may need, preserve that context or consider closing the issue before deletion. For a deleted issue you need back, contact your Jira administrator promptly.
Should I delete a completed subtask?
Usually, changing its status to complete or closed is clearer when the work was genuinely done. That keeps the issue visible for future reference and helps the parent’s history make sense. Deleting is more appropriate when the subtask was created accidentally, duplicates another issue, or has no continuing value to the team.
Conclusion
To delete a Jira subtask, open the parent, select the correct subtask, open its action menu, choose Delete, and confirm. Check the issue’s details and your team’s need for its history before taking that final step.
If the work is complete or may matter later, closing the subtask can keep useful context available. When the Delete option is missing, ask a project administrator to check your permissions. A quick review before deletion helps you clean up Jira without creating avoidable confusion for your team.