You cannot delete a ticket in Jira through the standard interface, but you can remove it from view or archive it depending on your permissions and what you need to accomplish

Jira does not have a delete button for individual tickets. Instead, the platform offers several ways to handle tickets you no longer need: you can resolve them (mark them as done), close them (end the workflow), move them to a different project, or — if you have administrator access — delete the entire issue through the database. Most teams use resolution and closure instead of deletion because Jira is designed to keep a record of all work, even completed or abandoned work.

The reason Jira works this way is practical: if someone deletes a ticket, any other tickets that link to it break, comments and attachments vanish, and you lose the history of why work was started and stopped. For most situations, marking a ticket as resolved or closed gives you the clean view you want without losing the audit trail.

Key Takeaways

  • Jira does not offer a delete option in the ticket view; instead, you resolve or close tickets to remove them from active work.
  • Resolving a ticket marks it as complete and moves it out of "open" views; closing a ticket ends its workflow entirely.
  • Only Jira administrators can permanently delete issues from the database, and doing so breaks links and removes all history.
  • If you need a ticket hidden from view without deletion, you can move it to an archive project or use filters to exclude resolved tickets.
  • Deleted tickets cannot be recovered, so administrators should confirm deletion is necessary before proceeding.

Resolve or close the ticket instead of deleting it

The most common way to remove a ticket from your active work is to resolve it. Open the ticket, click the blue button in the top right that shows the current status (usually "To Do", "In Progress", or "In Review"), and select "Resolved" or "Done" from the dropdown menu. The ticket stays in Jira with all its history intact, but it no longer appears in lists of open work.

If you want to go further and close the ticket entirely, follow the same process but select "Closed" instead. Some Jira workflows have a "Closed" status as the final step; others move directly from "Resolved" to "Closed". The exact options depend on how your team configured the workflow for that project.

Once a ticket is resolved or closed, you can still view it, search for it, and link other tickets to it. Comments and attachments remain visible. This is why most teams use resolution instead of deletion — you keep the record without the clutter.

Filter out resolved tickets from your view

If you have many resolved tickets cluttering your board or list, you do not need to delete them. Instead, use Jira's filter options to hide them. On your board or in your issue list, look for a "Filter" button or icon (usually a funnel shape). Click it and uncheck "Resolved" or "Done" to remove those tickets from the current view.

You can also create a saved filter that automatically excludes resolved tickets. In the left sidebar, click "Filters" and then "Create filter". Write a JQL (Jira Query Language) query like status != Resolved AND status != Closed and save it with a name like "Open Work Only". From then on, you can click that filter to see only active tickets.

Move the ticket to an archive project if your team uses one

Some Jira instances have an archive project where completed or abandoned work is moved rather than deleted. If your team has set one up, you can move a ticket there by opening it, clicking "Move" (usually in the "..." menu at the top right), and selecting the archive project as the destination.

This approach keeps the ticket in Jira and searchable, but moves it out of your main project so it does not clutter your board. The ticket retains all its history, links, and comments. Ask your Jira administrator whether your team has an archive project and whether you have permission to move tickets to it.

Permanently delete a ticket if you are an administrator

Only Jira administrators can delete tickets permanently. If you have administrator access and need to delete a ticket, open it and look for a "Delete" option in the "..." menu at the top right. Click it, confirm the deletion in the dialog that appears, and the ticket is removed from Jira entirely.

Deleting a ticket is permanent and cannot be undone. When you delete a ticket, any other tickets that link to it will show a broken link. Comments, attachments, and the full history of the ticket are removed. For this reason, administrators should delete only in rare cases — for example, if a ticket was created by accident or contains sensitive information that should not be in Jira at all.

If you are not an administrator and need a ticket deleted, contact your Jira administrator and explain why. They can review the request and decide whether deletion is appropriate or whether resolving the ticket would serve the same purpose.

Bulk delete multiple tickets if you have admin access

If you need to delete many tickets at once, Jira administrators can use the bulk delete feature. Go to "Issues" and run a search or filter to show only the tickets you want to delete. Click the checkbox at the top left to select all visible tickets, then click "Tools" and choose "Delete". Confirm the deletion in the dialog.

Bulk deletion follows the same rules as single deletion: it is permanent, breaks links, and removes all history. Use it only when you are certain the tickets should be removed entirely.

Frequently Asked Questions

Can I recover a ticket after I delete it?

No. Jira does not have an undo or recovery option for deleted tickets. Once deleted, the ticket and all its data are gone permanently. If you think you might need the ticket later, resolve or close it instead of deleting it.

What happens to linked tickets when I delete a ticket?

Any tickets that link to the deleted ticket will show a broken link. The linked ticket itself is not deleted, but the connection is broken and displays an error. This is one reason most teams avoid deletion and use resolution instead.

Why does Jira not let me delete tickets from the ticket view?

Jira is designed to keep a complete record of all work for audit and historical purposes. Deletion is restricted to administrators so that accidental deletions do not happen. For most situations, resolving or closing a ticket accomplishes what you need without losing the history.

Can I delete a ticket if I created it?

Only if you have administrator permissions. Regular users cannot delete tickets, even ones they created. You can resolve or close a ticket you created, but permanent deletion requires admin access. Contact your Jira administrator if you need a ticket removed.

Is there a way to hide a ticket without deleting or resolving it?

Yes. You can use filters to hide resolved tickets from your view, or move the ticket to an archive project if your team has one. You can also change the ticket's assignee or move it to a different project. These options keep the ticket in Jira but remove it from your current workspace.