You can delete a Jira ticket, but only if you have the right permissions

Deleting a Jira ticket is straightforward if your account has permission to do it — but most team members don't. Only project administrators, Jira administrators, and people with explicit delete permissions can remove tickets. If you try to delete a ticket and see no delete option, your account doesn't have that permission yet. You'll need to ask your Jira administrator to grant it, or ask them to delete the ticket for you.

The delete button appears in the same place for all Jira users who can access it, but the process differs slightly depending on whether you're using Jira Cloud (the online version) or Jira Server/Data Center (self-hosted). Both routes take less than a minute once you have permission.

Key Takeaways

  • Only Jira administrators and people with explicit delete permissions can remove tickets — most team members cannot.
  • In Jira Cloud, open the ticket, click the three-dot menu in the top right, and select Delete Issue.
  • In Jira Server or Data Center, open the ticket, click Tools in the left sidebar, and select Delete Issue.
  • Deleted tickets cannot be recovered, so make sure you're removing the right one before you confirm.
  • If you don't see a delete option, contact your Jira administrator to request delete permission or ask them to delete it for you.

Delete a ticket in Jira Cloud

Open the ticket you want to delete. Look at the top right corner of the ticket view — you'll see a three-dot menu icon (sometimes called the "more" menu). Click it.

A dropdown menu appears. Scroll down until you see Delete Issue. Click it. Jira will ask you to confirm the deletion — read the warning carefully, because deleted tickets cannot be restored. Click the red Delete button to confirm, or click elsewhere to cancel.

The ticket is now gone. Any links to it from other tickets or comments will show a "deleted issue" message, but the ticket itself no longer exists in your project.

Delete a ticket in Jira Server or Data Center

Open the ticket you want to delete. On the left side of the screen, you'll see a sidebar with several options. Look for Tools — it's usually near the bottom of that sidebar. Click it.

A menu expands. Click Delete Issue. Jira will show a confirmation dialog warning that the deletion is permanent. Read it carefully, then click the red Delete button to remove the ticket, or click Cancel to keep it.

Once you confirm, the ticket is deleted immediately. Unlike archiving or closing a ticket, deletion removes it completely from your Jira instance.

What happens to links and comments after you delete a ticket

When you delete a ticket, any other tickets that link to it will show a broken link or a message saying "deleted issue" instead of the ticket title. Comments that mention the deleted ticket by number will still exist, but clicking the ticket number won't work anymore.

If the deleted ticket was part of a sprint, it's removed from the sprint board immediately. If it was assigned to someone, that person will no longer see it in their work queue. There's no notification sent to the team — they'll only notice if they look for the ticket or see the broken link.

How to request delete permission if you don't have it

If you open a ticket and don't see a delete option, your account doesn't have permission. Contact your Jira administrator — this is usually someone in your IT department or a senior team member who manages Jira. Tell them you need to delete a specific ticket and ask them to either grant you delete permission or delete it themselves.

Most administrators can grant permission in a few minutes by adjusting your role or project permissions. If you only need to delete one ticket, it's often faster to ask them to do it directly rather than waiting for a permission change.

Alternatives to deleting a ticket

Before you delete a ticket, consider whether you actually need to remove it completely. Closing or resolving a ticket keeps it in your system for record-keeping but removes it from active work. This is useful if you want to keep a history of what was done or decided.

Archiving a ticket (available in some Jira versions) hides it from normal views but keeps it searchable and recoverable. Moving a ticket to a different project is another option if you created it in the wrong place. These alternatives are safer than deletion because you can undo them or find the ticket later if you need to reference it.

Frequently Asked Questions

Can I recover a ticket after I delete it?

No. Deleted tickets cannot be recovered in Jira Cloud, Server, or Data Center. If you delete a ticket by mistake, you'll need to create a new one and re-enter all the information. Always double-check the ticket number and content before confirming deletion.

What's the difference between deleting and closing a ticket?

Closing a ticket marks it as done but keeps it in your system. You can still see it, search for it, and reference it later. Deleting removes it completely — it won't appear in reports, searches, or project history. Close a ticket if you want to keep a record; delete it only if you never need to see it again.

Do deleted tickets affect my project reports?

Yes. Deleted tickets are removed from velocity reports, burndown charts, and historical data. If you delete a ticket that was part of a completed sprint, it won't show up in that sprint's final numbers. This is another reason to close tickets instead of deleting them — closed tickets still count toward your project history.

Can I delete multiple tickets at once?

Not through the standard delete button. You can delete tickets one at a time through the interface, or your Jira administrator can delete them in bulk using the database or automation tools. If you need to remove many tickets, contact your administrator instead of deleting them individually.

What if I don't have permission and my administrator won't grant it?

Your administrator may restrict delete permission for security or compliance reasons. In that case, ask them to delete the ticket for you, or close it instead. Closing achieves the same practical result — the ticket stops appearing in active work — without requiring delete permission.