You will need to find a backup of the system from before the deletion, restore that into a temporary system and then think about the best way to transfer the issue from the temporary system back into production. Deleting an issue really does mean a simple delete - it's removed, completely.
To embellish on Nic: Do not delete issues. I suggest closing with a resolution value of Deleted on anything you want to delete. I implement it with a special transition only the project lead can execute and it requires the fill in a reason field. When you delete it is GONE. Hardly a week goes by without someone wanting to restore an issue. 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 data that may have looked bad.
@Dusit this won't help you now, but maybe in the future. An alternative to deleting issues is to "move" them to another project. The trash project could be a place to store your unwanted issues in case you need to restore them one day. In the mean time you may be able to piece together the issue by referencing deleted JIRA notifications in your inbox.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs