How to make an issue undeletable (except by jira-admins)

[CST JIRA Confluence Admin]

We are using Tempo Timesheets for tracking chargeable clocking

For non-chargeable clocking (leave, training, etc.), we have an dedicated issue, where everyone in that JIRA project, clocks with no. of hours/days.

If Project admin by mistake, deletes this issue, its too cumbersome to restore using entire JIRA project, as that seems to be not easy way as well.

Also, we can't loose such important data, as it would be required sometime for many purposes.

Hence, we would need to have it to be un-delete-able except by JIRA-admins.

Any thoughts on possibilities, much appreciated

Thanks in advance

[Vasiliy Zverev]

You should not grant permission "delete issues" to project admins. Check permission schemas assotiated with projects.

[CST JIRA Confluence Admin]

But this stops from deleting all issues. What we need is, not to allow deleting only 1 issue (dedicated for non-chargeable clocking like leave, training, etc.), by anyone except Jira-admins. While others, are allowed to be deleted by project admins.

Maybe there's any possibilities to check if deleting user is Jira-admin, only then allow to delete. Others should be disallowed. 

[Niclas Sandstroem]

Why are you deleting issues in your projects? Answer that first and you might understand something is wrong in your process.

I would personally recommend the suggested approach from Vasiliy. If you need to delete some issues because of testing this can sent to the jira-administrators in a filter.

[CST JIRA Confluence Admin]

Just to clarify, Project admins, need to be given permission to delete anything except one issue. This will enable them to do house-keeping. We have 180+ projects, sending to Admin, seemingly lot of admin work & delay

Hope that this can be possible, else believe that usual way is via process.

[Nic Brough -Adaptavist-]

What good business reason is there for project admins being able to totally destroy data, forcing you to have to go back to a backup when they get it wrong?  You have a broken process right there.

What you could do is make it harder - make the issue have a different workflow to the others in the project, and then put "workflow properties" on each step that disallow the delete permission.

There are ways around that of course, but it'll stop them clicking "delete" initially.

The best fix though - remove "delete" permission from the permission scheme.  It should be limited to JIRA admins, or ideally, no-one.