# Epic FND-255 - Trash bin for deleted work packages

Project: Stream workspace foundations
Status: in review
URL: https://community.openproject.org/work_packages/FND-255

## Detailed specification

### Motivation and background information

### 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.

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2026 Q4 |
| Date |  |
| Votes | 32 |
| List | TIB 2026 |
| Target versions | 18.0.0 |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Work packages |
| Enterprise plan | Enterprise / Premium (PRE) |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Tom Hykel |
| Accountable |  |
| Product manager | Sonita Soth |
| Designer |  |
| Developers | OP Dev Comms Team |
| Requested by |  |
| Interest by | Bowling (40324) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

*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**

  - I have a chance to restore them if deleted by accident.

  - their data can be accessed in the baseline feature (<mention class="mention" data-id="26448" data-type="work_package" data-text="#26448">#26448</mention>)

**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