-
Suggestion
-
Resolution: Unresolved
-
5,591
-
1,132
-
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
-
JRACLOUD-23498 Recycle Bin for Jira Projects
- Closed
- is duplicated by
-
JRACLOUD-77509 Include a "soft-delete" in Jira, to mark issues as deleted but not delete them entirely from the database
- Closed
- is related to
-
JRACLOUD-59371 Provide an Audit Log for Deleted Issues in JIRA
- Gathering Interest
-
JRACLOUD-75496 Daily scheduled export of all the issues in a jira site
- Gathering Interest
-
JRACLOUD-81027 Ability to restore deleted attachments
- Gathering Interest
-
JRASERVER-36415 Have a Trash/Recycle Bin in JIRA
- Gathering Interest
-
ENT-1277 Loading...
- relates to
-
JRACLOUD-30430 Give a possibility to recover the deleted issue
- Closed
- causes
-
JST-493295 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- resolves
-
JST-492014 Loading...
-
JST-495395 Loading...