You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have deleted a ticket in a queue and would like to know if there is any way to recover a deleted ticket.
Hello,
You can recover a deleted ticket only by restoring your Jira from a backup. You should not let users delete tickets. Remove the Delete Issues permission from all users.
Hello Alexey,
I see. I will remove that option. How do you access a backup in Jira?
-Joon Cho
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
By default you can find backups in the JIRA_HOME/exports folder. But if you restore a backup, it will erase all changes made by you after the backup was taken.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As @Alexey Matveev says you should not delete issues
Do not delete issues. When you delete it is GONE. Hardly a week goes by without someone wanting to restore an issue. Deleting issues will come back and bite you when it is the most inconvenient. I suggest closing with a resolution value of Deleted anything you want to delete. I implement a special transition only the project lead can execute and it requires filling in a reason field from a select list (such as entered in error, OBE, Duplicate, Other) and explanation text.
Deleting issues destroys historical data. Missing issue numbers will eventually cause a question about what it was and why was it deleted even if it was done properly. Missing data always brings in the question of people hiding something that may have looked bad.
The only viable way to restore an issue is to create a new instance of JIRA and restore a backup that has the issues. Then export them to a csv file and import them to your production instance. You will lose the history.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I do not understand why they don't just make a server back-up and allow requests up to 30 days after, before purging files from back-up servers?
That's a proven way to keep data safe for your customers and an applied practice from many big companies. I realize it will require a bit more of a resource, but it is limited to 30days and this way you provide next level insurance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I completely agree. They keep whole projects for that time, so why not also just keep tickets? I can barely see how it'll make much difference resource wise, as I suspect in general it is a very few % of tickets in projects that are deleted every month.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.