# Feature OP-13495 - Optionally allow locked/closed versions for custom field

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-13495

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 13.1.0 |
| Sprint | 13.1.0 |
| 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 | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

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

## Estimates and progress

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

## Description

**As** a reporter of a bug (or a project manager later during edit)  
**I want to** be able to enter closed/locked version to the custom version field that is configured to accept non-open versions, e.g. "Affected version"  
**so that** a) I can add additional info related to non-open versions in a structured manner, b) I don't need to do this in plain text fields/description.

**Acceptance criteria**

  - Custom field of type Version can be optionally configured to accept closed and locked versions.
  - Such a field then accepts non-open versions as input, be it a single- or multi-select field.
  - Input is correctly stored, and can be then used, e.g. for filtering, if the custom field is configured so.

My initial idea is something like this:

<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/72405/content">

This would require another boolean for custom\_fields table and various changes around form API call. If you see additional things I'm missing here, please, let me know because I'd like to contribute this and would rather know about other possible complications from some core developer.