Content
View differences
Updated by Oliver Günther almost 4 years ago
_The intend of this work package was downscoped. Initially, it also included UI parts and deleting work packages permanently._
**As** an OpenProject user
**I want** work packages to land in a trash instead of being deleted permanently
**so that** that**
* I have a chance to restore them if deleted by accident.
* their data can be accessed in the baseline feature (#26448)
**Acceptance criteria**
* When the user deletes a work package, 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.
* Information flagged to be deleted is not visible in the UI/API any more except:
* when doing a baseline comparison where the information can be found if filtering for a point in time before the work package was deleted.
**Out of scope**
* A UI, even for admins, where deleted work packages can be seen.
* Any possibility to remove work packages permanently.
* Any possibility to restore work packages that have a deleted flag.
**Additional information** information**
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.
**Implementation notes**
* 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
* Remove the paper\_trail information on deleted work packages
**As** an OpenProject user
**I want** work packages to land in a trash instead of being deleted permanently
**so that**
* I have a chance to restore them if deleted by accident.
* their data can be accessed in the baseline feature (#26448)
**Acceptance criteria**
* When the user deletes a work package, 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.
* Information flagged to be deleted is not visible in the UI/API any more except:
* when doing a baseline comparison where the information can be found if filtering for a point in time before the work package was deleted.
**Out of scope**
* A UI, even for admins, where deleted work packages can be seen.
* Any possibility to remove work packages permanently.
* Any possibility to restore work packages that have a deleted flag.
**Additional information**
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.
**Implementation notes**
* 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
* Remove the paper\_trail information on deleted work packages