-
Suggestion
-
Resolution: Unresolved
-
6,409
-
1,212
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Today we have an update on Trash for Projects. We’re excited to announce that Trash for Projects is generally available as part of Jira Software.
Note that trash will work only for projects. It will not work for issues. We evaluated trash for issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future.
Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions. I am keeping this ticket as "Gathering Interest" so that you votes and comments can help us gather more information.
You can learn more about Trash for Projects at https://confluence.atlassian.com/adminjiracloud/trash-for-jira-software-and-jira-core-projects-1001820064.html
Regards,
Ritesh Ranjan
Product Manager, JIRA Platform
Sometimes, users will accidentally delete issues, and the steps to restore those issues usually involves restoring backups, which would take quite a lot of time and effort.
As such, it would be great if JIRA had some sort of Recycle Bin or Trash (like in Confluence) so that users would be able to restore any accidentally deleted issues easily.
Notes
Support are unable to recover accidentally deleted issues as per our data storage policy.
We encourage customers to regularly back up their products so they can always recover their data. See the following articles for more information:
- Jira products, see Exporting issues
- Confluence, see Create a site backup
You may also be able to recover data from your Sandbox instance if you have one.
Workaround Via third-party apps and API
- We can even use issue-history-for-jira and restore-deleted-issues marketplace add-ons that could help Track and restore deleted issues.
- If you are a premium and Enterprise customer then you can use the Archive Issues API option.
Preventive Workaround 
We can build this rule below to send a notification with information about the deleted issue in the future, using the Automation for Jira, a native feature in Jira.
Follows these steps to access the Automation for Jira: Jira >> settings >> System >> Automation rules
Email information to add in the rule:
SUBJECT
Issue deleted {{issue.key}} - {{issue.summary}}
CONTENT
This issue was deleted.
Issue Key: {{issue.key}}
Summary: {{issue.summary}}
Description: {{issue.description}}
Who delete the issue: {{initiator.displayname}}
You can have this email sent to a mailbox that you can go back to when you want to identify who deleted an issue.
- duplicates
-
- Closed
- is duplicated by
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
-
ENT-1277 Loading...
- relates to
-
- Closed
- causes
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- resolves
-
-
[JRACLOUD-36415] Have a Trash/Recycle Bin in JIRA for issues
Suffered an accidental issue delete today, and was shocked to find there was no Trash for Issues, especially considering Trash for Projects already deletes/restores issues in that context.
any update for this feature? At least we can undo what we accidentally delete
This is a must have feature that should be core functionality if you want to ensure a good user and customer experience. There are too many scenarios where an important issue can be deleted unintentionally. For some organisations this is also a requirement to help ensure record keeping guidelines/standards/legislation are properly complied to. Competitor products like Microsoft Azure DevOps restores deleted work items/issues from trash easily as an out-of-the-box feature.
Is there any update on this? Marketplace add-ons are cost prohibitive for this type of functionality which should be native to the product. This problem has presented itself multiple times where we cannot simply restore the entire instance (3500 users, 500 projects).
I strongly support the inclusion of the option to restore deleted or lost issues in the roadmap. This feature is critical for several reasons:
- Error Prevention: Accidental deletions can occur, and having a recovery option is essential.
- Data Security: It ensures that important information can be recovered in case of technical issues.
- User Confidence: Providing this safety net enhances the overall user experience.
I urge you to reconsider this decision, as it would greatly benefit users.
Thank you for your attention.
Best regards,
Adrian
Restoring deleted or lost issues is something that I consider a critical option. Please reconsider the decision to not include this in the roadmap.
Please implement the restoration mechanism. Businesses store the most important information in their systems that can be gone forever in 1 click.
Or display an alert to your customers "We have no backups for your information. Make sure to use 3rd party marketplace apps to keep your data in more than 1 place". Please don't ignore the obvious problem that is not acceptable in 2024 for such popular SaaS like yours.
https://getsupport.atlassian.com/browse/PCS-375034