• 4
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian update - 16 July 2020

      Hi everyone,

      Today we’re excited to announce that Trash for Projects is generally available as part of Jira Software.

      With “Trash” for projects, when a project is deleted it will be moved to “Trash” before it will be automatically deleted after 60 days. This will give a window to recover if projects were accidentally deleted. Projects can also be permanently deleted manually before the 60-day window expires.

      You can learn more about the feature at https://confluence.atlassian.com/adminjiracloud/trash-for-jira-software-and-jira-core-projects-1001820064.html 

      Regards,
      Ritesh Ranjan
      Product Manager, JIRA Platform
       

      When users inadvertently delete issue(s), getting them back is a royal PITA. Ie database restore, import into new instance etc, copy across somehow.

      Would be nice if deleted issues could be moved to a per-project recycle bin, as per confluence. That way if you needed to get them out they'd still have the same ID.

      BTW - I am aware of workarounds involving a Delete workflow action and issue security schemes, but I don't think that cuts it.

            [JRACLOUD-23498] Recycle Bin for Jira Projects

            Bill Bill added a comment -

            And of course, there is no API available

            Atlassian, you're killing me

            Bill Bill added a comment - And of course, there is no API available Atlassian, you're killing me

            Narendra Kumar added a comment - - edited

            Hi,

            Can anyone let me know that when a project is moved to trash, how many users will be notified through emails?  I mean what are the roles which will be getting mails ? Thanks!

            Narendra Kumar added a comment - - edited Hi, Can anyone let me know that when a project is moved to trash, how many users will be notified through emails?  I mean what are the roles which will be getting mails ? Thanks!

            d65d21771633  Can you clarify what you mean by test case?
            Currently trash will work for projects and all issues within the project. If you delete individual tickets, it will not be moved to Trash. You can follow this ticket https://jira.atlassian.com/browse/JRACLOUD-36415 for updates on trash for issues. 

            Ritesh Ranjan (Inactive) added a comment - d65d21771633   Can you clarify what you mean by test case? Currently trash will work for projects and all issues within the project. If you delete individual tickets, it will not be moved to Trash. You can follow this ticket  https://jira.atlassian.com/browse/JRACLOUD-36415  for updates on trash for issues. 

            @ritesh - Require a clarification -  is this trash feature only for "Projects" or even for test case level

            Nisath Jabeen added a comment - @ritesh - Require a clarification -  is this trash feature only for "Projects" or even for test case level

            d65d21771633 Trash for Projects will be available under Settings -> Projects -> Trash. It will be accessible only to admins, 

            Ritesh Ranjan (Inactive) added a comment - d65d21771633  Trash for Projects will be available under Settings -> Projects -> Trash. It will be accessible only to admins, 

            @ritesh Please let us know how to access the trash folder

            Nisath Jabeen added a comment - @ritesh Please let us know how to access the trash folder

            This is an absolute deal breaker. I cannot fathom why you'd not have this in place.

            Accidental deletes happen, especially with the current convoluted UI that's not user-friendly AT ALL. Expecting us to then reconstruct tickets (sometimes dozens of them) from notifications is a joke. The people whose conversations I'd need have left the business. Things are not static, and Jira should REALLY know that. Isn't that the whole point of the tool? To enable us to deal with changing requirements?

            Do as Notes or Photos does - deleted items are recoverable for 30 days. Even 1 day would be a lifesaver.

            Imola Unger added a comment - This is an absolute deal breaker. I cannot fathom why you'd not have this in place. Accidental deletes happen, especially with the current convoluted UI that's not user-friendly AT ALL. Expecting us to then reconstruct tickets (sometimes dozens of them) from notifications is a joke. The people whose conversations I'd need have left the business. Things are not static, and Jira should REALLY know that. Isn't that the whole point of the tool? To enable us to deal with changing requirements? Do as Notes or Photos does - deleted items are recoverable for 30 days. Even 1 day would be a lifesaver.

            It's unbelieveable that JIRA, a tool categorised as an Issue Tracker, doesn't have a built-in recovery method for deleted issues.

            A potential approach for building that tool could be:

            1. Create a Issue Security Level accessible just by the System, named 'Deleted'.
            2. Apply 'Deleted' Issue Security Level when a user selects More > Delete, instead of actually deleting the issue forever.
            3. Create a Recycle Bin page available just for users with JIRA Administrator permissions, where issues can be selected for recovery.

            This approach wouldn't actually move any issues to a trashcan, or any other place.

            It would just make so-deleted issues not viewable by any users, so that they do not interfere.

            Recovering issues would be as easy as removing the 'Deleted' Issue Security Level from the issue(s).

            Ignacio Pulgar added a comment - It's unbelieveable that JIRA, a tool categorised as an Issue Tracker, doesn't have a built-in recovery method for deleted issues. A potential approach for building that tool could be: Create a Issue Security Level accessible just by the System, named 'Deleted'. Apply 'Deleted' Issue Security Level when a user selects More > Delete, instead of actually deleting the issue forever. Create a Recycle Bin page available just for users with JIRA Administrator permissions, where issues can be selected for recovery. This approach wouldn't actually move any issues to a trashcan, or any other place. It would just make so-deleted issues not viewable by any users, so that they do not interfere. Recovering issues would be as easy as removing the 'Deleted' Issue Security Level from the issue(s).

            This is crucial for us, and surely for any other JIRA Cloud customers, provided that your Support T&C's don't cover any help for recovering deleted issues:

            Use of backup data to roll back changes to application data is not supported.

            So, deleted issues are lost forever.

            We have been offered the chance to restore our instance to a previous point in time as a favour, because even that task is not contractually supported.

            However, that was not a feasible solution at all, as we would have lost more data than which we tried to recover: all issues, comments and updates of a full workday.

            Please, reconsider including this feature in Atlassian's roadmap.

            Ignacio Pulgar added a comment - This is crucial for us, and surely for any other JIRA Cloud customers, provided that your Support T&C's don't cover any help for recovering deleted issues : Use of backup data to roll back changes to application data is not supported. So, deleted issues are lost forever. We have been offered the chance to restore our instance to a previous point in time as a favour, because even that task is not contractually supported. However, that was not a feasible solution at all, as we would have lost more data than which we tried to recover: all issues, comments and updates of a full workday. Please, reconsider including this feature in Atlassian's roadmap.

            version 5.0.3 - same issue.

            Ayelet (888) added a comment - version 5.0.3 - same issue.

              rranjan2 Ritesh Ranjan (Inactive)
              3a98194c076d Jamie Echlin
              Votes:
              61 Vote for this issue
              Watchers:
              35 Start watching this issue

                Created:
                Updated:
                Resolved: