We use Zabbix to monitor hardware. And we have seen over time that zabbix create and resolves a lot of issues I our Jira SM. about 75% of the issues are created and closed before any agents are involved in these issues.
We are tweaking these "alarms" in Zabbix, but there are a lot of old issues (about 100k) that we don't need, and would like to purge from the project.
I have read on this community that people are advised not to ever delete issues.
I would like to know if there are any problems we have to consider before deleting 75k issues that could break the system, or if the advisement is just related to historic data , revision etc.?
The reason we want to delete this issues is related to the time jira have to spend on indexing every time we do any changes to SLA or custom fields etc.
Hi @Jørgen Sandtorv ,
Please note: Once a ticket is deleted, it cannot be restored.
Thank you for your reply.
Can you also confirm that deleting issues does not result in any other problems than loosing the actual issues? There will be no problems with the database or elsewhere in Jira system/software because of deletion of a number of issues?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jørgen Sandtorv ,
Doing it in smaller batches will not impact anything.
As informed earlier, there could be performance issues during the deletion. So smaller the batches (depending on your system resources), better is the performance.
I would strongly suggest to do it after business hours or on Weekend when the load is very low.
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.
Keep me posted on the updates. Also please accept the answer if you find it useful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.