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
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.
Join now to unlock these features and more
I agree with @Joe Pitt's answer with regards to not deleting issues. I am a site admin myself and I have stripped the Delete Issues permission out for any user, including myself. Joe is correct this will always lead to loss of data and users eventually wanting to review previous issues.
However, I have to assume that your intention to delete an issue is not taken into account lightly. Neither did you ask the community what, if any, best practices there might be for deleting issues, rather you requested the method to delete issues.
If you can use an alternative method for "fencing/archiving" issues, such as the one stated by Joe, that would be the better option.
Hope this helps
This is extremely important to any regulated industries especially. There is material that can be erroneously added to a system that is required by law, in some cases, to be expunged.
In general I agree with the "never delete a ticket" crowd, accept when you need to purge material that should never have been there in the first place.
Do not delete issues. 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. Deleting issues will come back and bite you in the rear.
I suggest closing with a resolution value of Deleted and 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.
You can delete issues. Based on history in this forum it isn't a good idea. However, if you use Jira as a system of record you should not delete anything. Maybe I'm just old school, but if you're having lots of people making mistakes perhaps they need more training, not a change in the product.
@Boris Dzakula My stance is Jira is a system of record and you should close the issue with a resolution of something like entered in error or duplicate. Nothing should be deleted. Mistakes happen, but with so many people wanting to restore issues I believe you'll have more deletes by mistake than entered in error.