Is there a simple way to recover a deleted jira task?

[Sinclair]

I mean other than the IMO totally bonkers instructions here:

https://confluence.atlassian.com/jirakb/how-to-restore-accidentally-deleted-issue-in-jira-applications-313466155.html

Or can anyone recommend a plugin or extension or something that'll mean there's a trashcan for deleted things?

[Tarun Sapra]

Hello @Sinclair

Once the JIra issue is delete, it's completely gone and there is no way apart from the above mentioned link that I know of to retrieve the lost issue.

[Sinclair]

thanks for the help

[Sinclair]

I guess I'm working from a different perspective. It seems IMO a bit odd to not have an undelete function. It's something that exists in lots of other applications.

My workaround is to shift everything that may need deleting (e.g., duplicate jiras, etc) to a "Trashcan" epic for review.

Thanks for help everyone.

[Nic Brough -Adaptavist-]

Keeping an issue lurking in a deleted-but-not state is woolly thinking as well as highly inefficient. 

It's a poor design, but sadly one embedded in user's minds as they've become accustomed to it.

[Jack Brickey]

I concur with Nic and others here but would reiterate that you need to really consider why you would want to delete an issue at all instead of simply closing w/ an appropriate Resolution value, e.g. duplicate, won't do, not needed, mistaken creation, trash, etc. My point here is to handle the "trashcan" as a resolution value and not a status.

The only time i delete an issue is if I was creating some test issues and I don't want them cluttering my dashboard, metrics, etc. Deletion should be limited to System Admin or a very small group of folks that understand the responsibility and consequences.

[Joel Dale]

If Jira didn't just delete things forever, this question wouldn't even apply. If a trashcan existed, you'd not be needing to ask this question. 

In my case, I want my team to use subtasks. I expect these to come and go as their understandings change. And so I have every expectation to delete them. I have zero concerns about deleting subtasks. The fact that Jira sees everything as the same type ("Issue") is a failing of Jira in my opinion. 

It's just weird and wasteful to have garbage sitting around looking like it means something only to have a note or status or whatever, marking it 'done' but because it's not needed. Actually deleting truly unneeded things is clean and doesn't maintain noisy misinformation.

[Jack Brickey]

Personally I prefer to retain history but understand that doesn’t necessarily apply to everyone.

[Nic Brough -Adaptavist-]

The instructions are complex because there's no other way.  There are no "trash" add-ons either, as it's simply not supported.

This is why the standard recommendation is "never allow delete for most users".  Give them a resolution like "deleted" or "raised in error" so they can close issues they don't want with a good reason that can be ignored in reports.  Give them a "trash" project (all fields, all issue types, no permissions other than "create", "view" and "move").  Or give them a delete workflow status.  But don't allow simple delete.

[Gary Pasquale]

Hi @Sinclair,

Unfortunately, there is no simple way to recover a single issue. Once it's gone it's gone.

Hence why Jira will ask you "Do you really want to do this?" before deleting.

Prevention is better than cure in this instance. I'd advise restricting those who have the ability to delete issues. Project admins only is a good start.

The restoring from a backup is your only option if you do wish to recover data. Whether that be an XML back-up or a full system back-up. Be advised the XML back-up will not have any attachments.

Regards,

Gary

[Sinclair]

thanks for help