All tickets moved to one backlog

Question

We have several different backlogs. I was working to clean them up and deleted a backlog titled "old." When I deleted that backlog, all of the tickets in every backlog moved to our engineering backlog. Everything is disorganized now. I'm not sure how this happened as I never touched any tickets or other backlogs besides the old one. Is there anyway to move everything back to where it was??

Mary from Planyway · Answer

Hi @Kyli Kraft

It's Mary from Planyway

When you delete a backlog in Jira, the issues or tickets that were in that backlog do not get deleted; instead, they get moved to the default or main backlog. It seems like when you deleted the "old" backlog, the tickets from various backlogs might have been affected and moved to your engineering backlog. This situation can be quite disconcerting, but there are a few steps you can take to try and rectify it:

* Check the Audit Log: Review the audit logs in Jira to understand what exactly happened when you deleted the backlog. The audit log might give you clues about the changes made to the tickets and where they were moved.

* Review Ticket History: Each ticket in Jira keeps a history of the changes made to it. You can use this history to find out where each ticket was before the deletion of the backlog. This can be a bit time-consuming if you have a lot of tickets, but it's a reliable way to restore order.

* Use Filters and Labels: If you had specific filters or labels applied to tickets in different backlogs, you can use these to quickly identify and move the tickets back to their respective backlogs.

* Bulk Change: Once you have identified the tickets that need to be moved, you can use the "Bulk Change" feature in Jira to move multiple issues at once. This can save time compared to moving each ticket individually.

* Restoring from a Backup: If your Jira instance is regularly backed up, you might consider restoring it to a point before the backlog was deleted. This can be a drastic step and might result in loss of any changes made after the backup point, so it should be considered carefully.

* Contact Atlassian Support: If you're unable to sort out the issue, contacting Atlassian Support might be helpful. They could provide more specific guidance or assistance, especially if there’s a complex issue at play.

* Prevent Future Issues: Once resolved, it might be wise to review your Jira configuration and user permissions to prevent similar mishaps in the future. Training and clear guidelines on managing backlogs and issues can also be beneficial.

Fabian Lim · Answer

Hi @Kyli Kraft

Welcome to the community!

Are these tickets all from the same Jira Project and you have multiple boards within the project for the various teams? or are they separate projects in a single board?