# Feature OP-8057 - Keep names of locked users in custom fields of type user

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-8057

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

# Description 

AS an OpenProject user   
I WANT user selections to remain valid post deactivation of said user  
SO THAT I can retain details about a work package even after the user is no longer active

# Acceptance Criteria

  - In the work package support 
      - Remove locked users from the list of available users
      - Retain locked users as a selection even after the user has been locked

# Current Behaviour

  - If a user has been locked, and you attempt to edit the work package, you receive the following error: {Field Name} is not set to one of the allowed values.
  - Ideally, we'd be able to retain the user's name in the field after the user has been expired for historical purposes
