You can delete a Jira ticket, but Jira makes it harder than creating one
Deleting a Jira ticket requires you to have project admin or higher permissions, and the process differs depending on whether you are using Jira Cloud or Jira Server/Data Center. In Jira Cloud, you navigate to the ticket, open the menu, and select Delete. In Jira Server or Data Center, the delete option lives in the issue menu as well, but your instance administrator may have disabled deletions entirely.
Most teams do not delete tickets — they close them or mark them as duplicate instead — because deletion is permanent and leaves no record of what was removed. Once you confirm, the ticket and all its comments, attachments, and history disappear completely. There is no trash or recovery option.
Key Takeaways
- Deleting a ticket requires project admin permissions or higher; regular users cannot delete tickets they created.
- Jira Cloud and Jira Server/Data Center have slightly different delete workflows, and some instances disable deletion completely.
- Most teams close or mark tickets as duplicate instead of deleting them, because deletion removes all history and cannot be undone.
- If you cannot find a delete option, your Jira administrator may have turned off deletions for your project or instance.
How to delete a ticket in Jira Cloud
Open the ticket you want to delete. In the top right corner, you will see a three-dot menu icon. Click it and look for the Delete option — it is usually near the bottom of the menu, sometimes labeled as "Delete issue" or simply "Delete".
Click Delete. Jira will ask you to confirm. Read the warning carefully: deletion is permanent and cannot be reversed. Once you confirm, the ticket and all its comments, attachments, and history disappear completely. If you do not see a Delete option in the menu, you do not have permission to delete tickets in this project. Contact your project administrator or Jira administrator to request the necessary permissions.
How to delete a ticket in Jira Server or Data Center
Open the ticket. Look for the Tools menu or a three-dot menu in the top right. Click it and select Delete Issue. The confirmation dialog will appear. Confirm the deletion, and the ticket is removed.
Some Jira Server and Data Center instances have deletion disabled at the instance level. If you see no delete option anywhere, your Jira administrator has turned it off. This is common in organizations that need to keep all issue history for compliance or audit reasons. You will need to ask your administrator to either enable deletions or delete the ticket for you.
Why most teams do not delete tickets
Deleting a ticket removes everything: the description, all comments, linked issues, time tracking, and the entire conversation history. If someone searches for that ticket later or tries to understand why a decision was made, the information is gone. This creates blind spots in your project history.
Instead, most teams close the ticket with a status like Closed, Done, or Wontfix, or they mark it as a duplicate and link it to the ticket that supersedes it. This keeps the record intact while removing it from active work. If you created a ticket by mistake, marking it as duplicate is cleaner than deletion.
What permissions you need to delete a ticket
You must have at least project admin permissions to delete a ticket in most Jira configurations. Some instances require Jira administrator permissions instead. Regular project members, even if they created the ticket, cannot delete it.
If you are the project lead or project admin, you should have delete permission by default. If you are not sure whether you have it, try opening a ticket and looking for the delete option. If it is not there, contact your Jira administrator and ask whether deletions are turned on for your project and whether you have the right permissions.
Deleting multiple tickets at once
Jira does not have a bulk delete feature in the user interface. If you need to delete many tickets, you have two options: delete them one at a time through the UI, or ask your Jira administrator to delete them using the database or a script.
For a small number of tickets, one-at-a-time deletion is straightforward. For dozens or hundreds, contact your administrator. They can often do it faster and can also generate a report of what was deleted, which is useful for compliance or record-keeping purposes.
What happens to linked issues and comments when you delete
When you delete a ticket, all linked issues lose that link. If another ticket references the deleted one, that reference becomes a broken link. Comments and attachments are also deleted permanently.
Before you delete, check whether the ticket is linked to anything important. Open the ticket and look at the Links section on the right side. If it has links to other tickets, consider closing it instead of deleting it, so the link history remains intact and other team members can still see the relationship.
Frequently Asked Questions
Can I undo a deletion?
No. Once you confirm deletion, the ticket is gone permanently. There is no undo, no trash, and no recovery option. If you delete a ticket by mistake, you will need to recreate it manually or ask your Jira administrator whether they have a backup they can restore from.
What is the difference between deleting and closing a ticket?
Closing a ticket changes its status to Done, Closed, or a similar final state, but keeps all the history, comments, and links intact. Deleting removes the ticket entirely. Closing is reversible; deletion is not. Most teams close tickets instead of deleting them.
Why do not I see a delete option?
You either do not have project admin permissions, or your Jira administrator has disabled deletions for your instance. Ask your administrator to check your permissions or to enable deletions if they are turned off.
Can I delete a ticket if it has a subtask?
No. If a ticket has subtasks, you must delete the subtasks first, then delete the parent ticket. Jira will not let you delete a parent issue while subtasks still exist.
Should I delete a ticket or mark it as duplicate?
Mark it as duplicate. This keeps the ticket in your history, links it to the ticket that supersedes it, and makes it clear why the ticket was closed. Deletion removes all context and makes it impossible to understand the decision later.