# Feature OP-19981 - Custom Version field does not list work packages in the assigned version

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| 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 | Administration / Custom fields |
| Feature Flag |  |
| Requires doc change | No |
| 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

**As** a OpenProject user who uses custom fields to manage work package versions

**I want to** have work packages assigned to a version through a custom Version field also be listed on the corresponding version

**so that** custom Version fields provide the same version-related functionality as the built-in Version field, and I can use custom fields without losing the ability to see all related work packages in a version.

**Acceptance criteria**

*   When a work package has a value assigned in a custom field of type **Version**, the work package is also listed in the corresponding Version.
    
*   The behavior is consistent with the existing built-in **Version** field.
    
*   If the custom Version field is changed to another version, the work package is removed from the previous version and listed in the newly selected version.
    
*   If the custom Version field is cleared, the work package is no longer listed in the previously assigned version.
    
*   Multiple custom Version fields can be used without causing incorrect or duplicate version assignments.
    
*   Existing work packages and existing custom Version fields continue to work as before after the feature is introduced.
    
*   The functionality applies wherever OpenProject currently uses the Version relationship to list or display related work packages.
    

**Current behaviour**

*   Work packages assigned via the built-in **Version** field are listed in the corresponding version.
    
*   Work packages assigned via a **custom field of type Version** are **not** listed in the corresponding version.
    
*   The custom Version field stores the selected version on the work package, but does not create the same relationship between the work package and the version as the built-in field.
    
*   As a result, the built-in Version field and custom Version fields behave differently despite both referencing a version.
