# Epic AUTOWORK-299 - Archiving of values from contextual custom fields

Project: Stream Workflows & Automations
Status: in specification
URL: https://community.openproject.org/work_packages/AUTOWORK-299

## Detailed specification

### Motivation and background information

When custom field items are contextualized at project level (<mention class="mention" data-id="AUTOWORK-283" data-type="work_package" data-text="#AUTOWORK-283">#AUTOWORK-283</mention>) there is currently no way to "retire" an item that is no longer relevant without losing historical data. Without archiving, admins face a dilemma: either leave outdated items selectable (risking incorrect entries) or delete them (losing traceability on historical records).

**Goal**

Allow global/project admins to archive individual values of a project-contextualized custom field, so that archived items are no longer offered for selection but remain displayed in the work packages they were previously assigned to.

### Acceptance criteria

<br>

*   An archived item no longer appears in selection dropdowns for new or edited work packages
    
*   An archived item remains displayed on all work packages where it was previously set, with a visual distinction
    
*   Archiving and unarchiving are available in the project settings
    
*   Bulk archiving of multiple items is supported?
    
*   Archiving does not remove the value from any existing work package
    
*   Archived values remain availablein work package filters and saved queries

### Out of scope

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

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q2 |
| Date |  |
| Votes |  |
| List |  |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Sonita Soth |
| Accountable | Rosanna Sibora |
| Product manager | Sonita Soth |
| Designer | Parimal Satyal |
| Developers | OP Dev Sirius Team |
| Requested by |  |
| Interest by | Home (224196000003952096), Prism (924316000001824179) |

## Estimates and progress

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

## Description

**User Story**

1.  As a global admin, I want to archive a value of a custom field for a project, so that team members can no longer pick it when they create or edit work packages.
    
2.  As a project member, I want to still see the archived value on work packages where it was picked before, so that nothing gets lost and we can trace what happened.
    
3.  As a project member, I want to see a clear sign (indication in the UI) on a work package that its value is archived, so that I understand why it is missing in the list for new entries.
    
4.  As a global admin, I want to restore an archived value, so that it can be picked again if things change.
    
5.  As a global admin, I want to filter the values of a custom field by status (active or archived), so that I quickly see which values are still in use and which are &quot;retired&quot;.
    
6.  _For a Project admin_&nbsp;
    
    1.  As a global admin, I want to control with a permission whether project admins are allowed to archive and restore values in their project, so that I decide who can change it.
        
    2.  As a project admin with this permission, I want to archive and restore values in my project, so that my team only picks values that are still valid.
        
7.  As a project memeber, I want to filter work packages by archived values, so I can still see historical data