Begin of the insertion_The intend of this work package was downscoped. Initially, it also included UI parts and deleting work packages permanently._

End of the insertion **As** an OpenProject user
**I want** work packages to land in Begin of the insertionaEnd of the insertion Begin of the deletion theEnd of the deletion trash Begin of the insertioninstead ofEnd of the insertion Begin of the deletion beforeEnd of the deletion being deleted permanently
**so Begin of the insertionthat** 

* End of the insertion Begin of the deletion that**End of the deletion I have a chance to restore them if deleted by accident. Begin of the insertion
* their data can be accessed in the baseline feature (#26448)End of the insertion

**Acceptance criteria**

* Begin of the insertionWhen the user deletes aEnd of the insertion Begin of the deletion don't deleteEnd of the deletion work Begin of the insertionpackage, their data (including relations, journals and attachments) don't get removed from the data base and file storage any more. Instead, this information is flagged to be deleted.End of the insertion Begin of the deletion packages permanently right awayEnd of the deletion
* Begin of the insertionInformation flagged to be deleted is not visibleEnd of the insertion Begin of the deletion allow viewing work packagesEnd of the deletion in Begin of the insertionthe UI/API any more except:End of the insertion Begin of the deletion trashEnd of the deletion
* Begin of the deletion perhaps add filter and query "in trash"
* allow deleting work packages in trash for good

**Discussion**

EvenEnd of the deletion when Begin of the insertiondoing a baseline comparison whereEnd of the insertion Begin of the deletion emptyingEnd of the deletion the Begin of the insertioninformation can be found if filtering for a pointEnd of the insertion Begin of the deletion trash we could argue that work packages should remainEnd of the deletion in Begin of the insertiontime beforeEnd of the insertion the Begin of the insertionwork package was deleted.

**Out of scope**

* A UI,End of the insertion Begin of the deletion databaseEnd of the deletion even Begin of the insertionfor admins, where deleted work packages canEnd of the insertion Begin of the deletion if inaccessible. Especially important wouldEnd of the deletion be Begin of the insertionseen.
* Any possibilityEnd of the insertion to Begin of the insertionremove work packages permanently.
* Any possibilityEnd of the insertion Begin of the deletion keep the journalsEnd of the deletion to Begin of the insertionrestoreEnd of the insertion Begin of the deletion see who deleted aEnd of the deletion work Begin of the insertionpackages that have a deleted flag.End of the insertion Begin of the deletion package in the end.End of the deletion

Begin of the insertion**Additional information** 

End of the insertion We keep getting inquiries by users who claim that work packages magically disappeared. Still having the journals around showing when a work package was deleted and by whom would help us a lot here.

Begin of the deletion Setting confidence as low as it isn't an easy thing. Maybe it would be enough to have a general auditing feature without trash to address the point above but that wouldn't really help users getting their 'missing' data back.

End of the deletion **Implementation Begin of the insertionnotes**End of the insertion Begin of the deletion Notes**End of the deletion

* we should look into using db views based on a deleted\_at column to implement this
* this way no existing queries would need to be changed at all