You cannot delete a Jira ticket once it exists, but you can close it or move it to a Done status

Jira is designed to keep a record of every ticket ever created, so the delete button does not exist for regular users. This is intentional — teams need to see what work was attempted, what was decided, and why something was abandoned. Instead of deletion, you mark a ticket as Done, Closed, or Resolved depending on your team's workflow, or you can move it to a custom status that means "not doing this."

If a ticket was created by mistake and contains sensitive information, you have a few options: ask a Jira administrator to delete it (they can, but it requires permissions most people do not have), move it to a private project, or straightforward close it and mark it as a duplicate or invalid. Most teams use the close-and-mark approach because it preserves the history of why the ticket was not completed.

Key Takeaways

  • Jira does not allow deletion of tickets by default because teams need a record of all work attempted, including what was rejected or abandoned.
  • The standard approach is to change the ticket status to Done, Closed, or Resolved using your team's existing workflow, not to remove it.
  • If a ticket was created in error, mark it as a duplicate or invalid and add a comment explaining why, so the reason is visible to the team.
  • Only Jira administrators with specific permissions can permanently delete a ticket, and this is rarely done because it breaks the audit trail.
  • If a ticket contains sensitive data, ask your administrator to delete it or move the ticket to a restricted project rather than leaving it visible to the whole team.

How to close or resolve a ticket instead of deleting it

Open the ticket you want to close. In the top right or along the right sidebar, you will see a button labeled "Transition" or a dropdown showing the current status (such as "To Do" or "In Progress"). Click that button or dropdown.

A menu will appear showing the statuses your team's workflow allows. Select "Done," "Closed," "Resolved," or whatever your team calls the final state. Some workflows have multiple end states — for example, "Done" for completed work and "Won't Do" for rejected work. Choose the one that matches what happened to the ticket.

Add a comment if the reason for closing is not obvious from the ticket history. For example, if you are closing a ticket because it was a duplicate, write "Duplicate of PROJ-1234" so anyone reading the ticket later understands why it was not completed. Click "Save" or "Transition" to confirm.

Marking a ticket as a duplicate or invalid

If the ticket should never have been created, use the status or label your team reserves for that purpose. Common approaches are to transition it to "Invalid," "Won't Do," or "Duplicate," or to add a label like "duplicate" or "rejected."

In the ticket details, find the "Link" button or option (usually in the right sidebar under "Link Issue"). Click it and select "is duplicated by" or "duplicates" depending on which ticket is the original. Then enter the ticket number of the original ticket — for example, PROJ-1234. This creates a visible link between the two tickets so anyone reading either one can see the relationship.

Transition the ticket to your team's "closed without work" status and add a comment with the reason. This keeps the ticket in the system for audit purposes but makes it clear it was not a real piece of work.

When you need a Jira administrator to delete a ticket

Jira administrators have the ability to permanently delete tickets, but this power is restricted because deletion removes the ticket from all reports, search results, and the audit log. Most organizations discourage deletion because it makes it impossible to answer questions like "Why did we stop working on this?" or "Did we ever consider this feature?"

If a ticket contains sensitive information — passwords, personal data, or confidential business details — ask your Jira administrator to delete it. Provide the ticket number and a brief explanation. The administrator will need to log in with admin credentials and use the "Delete" option in the ticket's menu. This is a permanent action and cannot be undone.

If deletion is not an option, ask the administrator to move the ticket to a restricted project that only certain team members can see, or to restrict the ticket's visibility so only project leads can view it. This keeps the ticket in the system for your own records while hiding it from people who should not see it.

Bulk closing multiple tickets at once

If you need to close many tickets — for example, closing all tickets from a cancelled project — use Jira's bulk change feature instead of closing them one by one. Go to your project and use the filter or search to show only the tickets you want to close. For example, you might search for "status = 'To Do' AND project = PROJ" to find all unstarted tickets in a project.

Once the list appears, look for a "Tools" menu or checkbox at the top of the list. Select "Bulk Change" or "Select All." A menu will appear asking what you want to change. Select "Change Status" and choose the status you want to explore to all selected tickets. Add a comment that will be posted to all of them — for example, "Project cancelled" — and confirm.

Jira will process the bulk change in the background. Depending on how many tickets you are closing, this may take a few minutes. You will see a notification when it is complete.

What happens to a closed ticket

Once a ticket is closed or moved to Done, it no longer appears in most team views by default. When someone filters for "open tickets" or "to do," closed tickets are hidden. However, the ticket still exists in Jira and can be found using search or by changing the filter to show closed tickets.

Closed tickets still appear in reports that track completed work, velocity, or historical trends. They remain linked to any other tickets that reference them. Comments, attachments, and the full history of the ticket remain visible to anyone with access to the project.

If you need to reopen a ticket that was closed by mistake, click the "Transition" button again and select "Reopen" or move it back to "To Do." This is a normal action and does not require administrator permissions.

Archiving or hiding old tickets

Some teams use Jira's archive feature to hide old, completed work without deleting it. This is available in Jira Cloud but not in all versions of Jira Server or Data Center. If your team uses Jira Cloud, you can archive a project to hide all its tickets from regular searches while keeping them available if someone specifically looks for them.

To archive a project, go to the project settings (usually a gear icon), find "Archive Project," and confirm. The project and all its tickets will be moved to an archive section. You can still search for archived tickets and view them, but they will not appear in dashboards or regular project lists.

If you only want to hide a single ticket rather than an entire project, the best approach is to move it to a "Done" or "Closed" status and trust that your team's filters will hide it from daily view. There is no single-ticket archive feature in most Jira versions.

Frequently Asked Questions

Can I undo a ticket deletion if an administrator deleted it?

No. Once an administrator permanently deletes a ticket, it cannot be recovered. This is why most teams close tickets instead of deleting them. If you think a ticket was deleted by mistake, contact your Jira administrator when ready — they may be able to restore it from a backup, but only if they act quickly.

What is the difference between closing a ticket and resolving it?

The difference depends on your team's workflow. Some teams use "Resolved" to mean the work is done and "Closed" to mean it has been reviewed and approved. Others use them interchangeably. Check your team's workflow definition in Jira settings to see what each status means in your project.

If I close a ticket, can other team members still see it?

Yes. Closed tickets are still visible to anyone with access to the project. They just do not appear in filters that show only open tickets. If you need to hide a ticket from certain people, ask your administrator to restrict the ticket's visibility or move it to a private project.

Can I delete a ticket I created if no one else has worked on it?

No. Regular users cannot delete any ticket, regardless of whether anyone has worked on it. You can only close it or ask an administrator to delete it. The standard practice is to close it and mark it as invalid or a duplicate.

What should I put in the comment when I close a ticket by mistake?

Write something clear like "Closed in error — reopening" or "Duplicate of PROJ-5678." This way, anyone reading the ticket history later will understand what happened and why the ticket status changed. If you are closing it because it is no longer needed, write "Project cancelled" or "Feature deprioritized" so the reason is documented.