How to Delete a Jira Issue: Steps and Permissions Guide
Need to delete an issue in Jira? Learn the steps, check permissions, and protect important history. Click to discover how to delete issue Jira safely.
Deleting a Jira issue can clear clutter quickly, but one wrong click may remove work history your team still needs. The delete option may also be missing, even when you can edit the issue, because Jira checks a separate permission.
But here's the truth: deletion is usually straightforward once you confirm the issue is safe to remove and your project grants the right access. Here's why that matters: deleting an issue can remove its comments, attachments, links, and other history, depending on the issue and project setup.
In this guide, I’ll walk you through the steps, explain the permissions to check, and show you what to review before confirming. You’ll also learn when closing or moving an issue is safer than deleting it. That way, you can remove a test ticket without accidentally losing a useful record of work.
How to Delete a Jira Issue
Open the issue, choose Delete from its actions menu, and confirm. You need the project’s Delete Issues permission; being able to edit an issue does not automatically give you permission to delete it.
Confirm that deletion is appropriate. Check the issue key, summary, comments, attachments, links, and any related work. If your team may need the issue history later, consider closing it or moving it instead.
Open the issue. Go to the Jira project and select the issue you want to remove. Verify its key and summary before taking action; similar issue titles can make the wrong ticket easy to select.
Open the issue actions. Select the three-dot menu or the More menu on the issue page. The placement and label can vary with Jira’s interface and project configuration.
Select Delete. If the option is missing or unavailable, ask a project or Jira administrator to check your permissions. You may have permission to edit the issue but not to delete it.
Review the confirmation prompt. Read any warning about related items, such as subtasks, and confirm you have selected the intended issue. The prompt can vary depending on the issue and project setup.
Confirm the deletion. Select the final confirmation button only when you are sure. Then check the project or issue search to make sure the intended issue no longer appears.
Jira’s menus can differ between Cloud and self-managed deployments, and between project types. If your screen looks different, look for the issue’s actions menu and ask your administrator about the project’s deletion settings.

What Permission Do You Need?
Jira controls issue deletion through the Delete Issues project permission. That permission is separate from issue editing, so a person who can update a summary or change an assignee may still be unable to delete the issue.
In many company-managed projects, an administrator can review the project’s permission scheme and see which roles, groups, or individual accounts have the permission. Team-managed projects use project-specific access settings, so the steps to grant access may differ.
For example, you might be a project administrator who can manage versions but still lack the permission to delete issues. Ask a Jira administrator to check your project access rather than requesting broader access than you need.
What to Ask Your Administrator
Does my account have the Delete Issues permission in this project?
Is the project company-managed or team-managed, and where are its permissions controlled?
Does a team policy require approval before an issue is deleted?
Could deleting this issue affect subtasks, linked work, or reports the team relies on?
Grant deletion access carefully. If someone only needs to remove a single test issue, an administrator may prefer to review the request and perform the deletion rather than grant ongoing access.
What Happens When You Delete an Issue?
Deleting an issue removes it from the project as an active Jira issue. Its comments, attachments, and recorded activity may also be removed, and the issue’s history may no longer be available through the usual project screens.
Consider a ticket that looks like a duplicate but contains a useful troubleshooting note. Deleting it could erase that note along with the issue. Linking it to the primary ticket and closing it may preserve helpful context for someone investigating the same problem later.
Related items deserve a closer look. Jira may show a confirmation prompt when an issue has subtasks or other relationships, but the exact behavior can depend on the project and configuration. Review the prompt and check with your administrator if you are unsure what will happen.
Review Before You Confirm
Issue details: Confirm the issue key and summary match the ticket you intend to remove.
Comments and attachments: Check whether they contain useful decisions, evidence, or work notes.
Subtasks and links: Look for related work that might need to remain accessible.
Team requirements: Check whether your organization expects an approval or retention process.
Jira’s ordinary delete action should be treated as difficult to reverse. Don’t assume a deleted issue can be restored easily; ask your administrator about your organization’s recovery options before you proceed.
Should You Delete, Close, or Move the Issue?
Choose deletion when an issue is genuinely unwanted, such as a mistaken test ticket with no useful history. Choose closure when the work is finished or no longer planned. Closing keeps the issue available for searches and future reference.
Moving an issue to another project can make sense when it belongs in a different team’s workspace. Linking a duplicate to the main issue and closing it can help people understand what happened without keeping two active tickets.
For example, imagine two tickets describe the same login error. Instead of deleting one immediately, link it to the ticket the team is tracking, add a short explanation, and close the duplicate. That leaves a useful trail for someone who later searches using the duplicate’s wording.
Choose the Action That Fits
Delete: Remove a mistaken or unwanted issue when its history and related details are not needed.
Close: Keep a completed, rejected, or duplicate issue available for later reference.
Move: Put an issue in a more suitable project when the work still needs to be tracked.
Link: Connect related or duplicate issues so the team can follow their relationship.
But here's the truth: the quickest option is not always the clearest one for your team. If people may need the issue’s history, closing or linking it can prevent confusion later.
Deleting Several Issues at Once
If you need to remove several Jira issues, check whether your Jira setup offers a bulk change process and whether your account has the required access. Bulk actions can affect many tickets at once, so review the selection before confirming.
Start with a narrow search that identifies only the issues you intend to remove. Review the results, confirm the issue keys, and check whether your team requires approval. A query that includes one extra project or issue type could turn a small cleanup into a much larger deletion.
Bulk operations may require access beyond the permission to delete a single issue. If the bulk delete action is unavailable, ask your Jira administrator to confirm the required permissions and whether bulk deletion is allowed in your environment.
A Safer Bulk-Deletion Routine
Write down the reason for the cleanup and the criteria for selecting issues.
Run a search using those criteria, then inspect the results for unexpected issues.
Ask a teammate or administrator to review the selection if the impact could be significant.
Use the bulk change option, if available, and read each confirmation screen carefully.
Check the project after the action and report any unexpected results promptly.
For a small number of tickets, deleting them individually can make it easier to verify each one. For a larger cleanup, careful review matters more than speed.
Issue Management with ONES.com
ONES.com brings project management and knowledge management together, with ONES Project for project work and ONES Wiki for team knowledge. If you are considering a Jira alternative, compare how each platform handles issue permissions, work history, and team processes before making a change.

Core Capabilities
Disconnected project and knowledge work: ONES.com combines project management with knowledge management, helping teams keep work tracking and team knowledge in one platform.
Jira migration concerns: ONES Project offers Jira-compatible workflows, which can help teams carry familiar processes into a Jira alternative.
Rigid issue processes: Custom workflows and fields let teams shape how work moves and what information each issue captures.
Limited sprint visibility: Sprint management helps teams organize planned work and follow progress during a development cycle.
Manual repetitive tasks: Automation can reduce recurring steps in project workflows and free up time for team work.
Hard-to-read project status: Built-in reporting gives teams ways to review progress without relying only on individual issue screens.
Too many add-ons: Native capabilities can reduce reliance on plugins for common project management needs.
Deployment requirements: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployment options, with feature parity between cloud and self-hosted versions.
Small-team evaluation: The free plan supports up to 30 seats, giving a team room to assess the platform before deciding how to proceed.
Application Scenarios
A software team reviewing its Jira setup: The team can evaluate Jira-compatible workflows, custom fields, sprint management, and reporting in ONES Project. It can also consider ONES Wiki for team knowledge management, with each product sold separately.
An organization with deployment constraints: A team that cannot use a cloud-only service can assess On-Premise, Private Cloud, or Air-gapped deployment options alongside Cloud. Comparing deployment needs with workflow requirements can help clarify whether the platform fits.
ONES.com is an option to assess when your team wants project and knowledge management capabilities across different deployment models. Review your permissions, issue lifecycle, and migration requirements as part of any platform evaluation.
Common Challenges When Deleting Jira Issues
The Delete Option Is Missing
Problem: You can open and edit an issue, but its actions menu has no Delete option. Solution: Ask a project or Jira administrator to check your Delete Issues permission and project access settings.
You Are Unsure Whether the Issue Is a Duplicate
Problem: Two issues look similar, but one may contain unique notes or investigation history. Solution: Compare their details, link the duplicate to the issue being tracked, and close it if its history may still help the team.
The Issue Has Related Work
Problem: The issue has subtasks or links, and you are unsure how deletion will affect them. Solution: Review Jira’s confirmation prompt, inspect the related work, and ask an administrator before confirming if the outcome is unclear.
You Need to Remove Many Issues
Problem: A large selection raises the risk of deleting tickets that should remain. Solution: Use precise search criteria, inspect the full selection, and arrange a second review before using a bulk action.
Frequently Asked Questions
Can I delete a Jira issue if I can edit it?
Not necessarily. Editing an issue and deleting it are controlled by different permissions. Your account needs the project’s Delete Issues permission to remove an issue. If the delete action does not appear, ask a project or Jira administrator to check your access. Avoid requesting broader permissions than you need for the task.
Can a deleted Jira issue be restored?
Do not assume that a deleted issue can be restored through the normal Jira interface. Recovery options can depend on your Jira deployment, administrative setup, and recovery practices. If the issue contains important work history, check with your administrator before deletion. Closing or linking the issue may be safer when the team could need that history later.
Does deleting an issue also delete its subtasks?
The effect on subtasks and related work can depend on the issue and project setup. Jira may show a confirmation prompt that explains what will happen. Read that prompt carefully instead of assuming related items will remain unchanged. If the message is unclear, ask your Jira administrator before confirming the deletion.
Can I delete Jira issues in bulk?
Some Jira environments provide bulk change actions, but access and availability can vary. You may need additional permissions beyond those required to delete one issue. Use a precise search, inspect every selected result, and check your team’s approval rules before proceeding. If the bulk action is missing, ask an administrator whether it is available in your project.
Is closing an issue the same as deleting it?
No. Closing an issue changes its status so the team can see it is finished, rejected, or no longer active. Deleting removes it from the project as an active issue and may remove its history and related details. Close an issue when people may need to review its past work; delete it only when that history is not needed.
Conclusion
To delete a Jira issue, open it, choose Delete from its actions menu, and confirm the prompt. You also need the project’s Delete Issues permission, which is separate from permission to edit an issue.
Before you confirm, verify the issue key and consider its comments, attachments, subtasks, and links. If the ticket may help someone later, closing or linking it can preserve useful context. For bulk removal, review the complete selection and follow your team’s approval process.
A careful check can prevent a quick cleanup from turning into lost work history. When deletion is the right choice, confirm the permission and the issue details first; when it is not, choose the action that keeps your team’s work understandable.