# Feature OP-16127 - Dynamic filtering of custom field dropdown

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 2 |
| 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 |  |
| 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 user from the e.g. "Development" department who wants to use a custom field with a list datatype, which includes multiple values  
**I want** the custom field dropdown to display only the values related to the "Development" department  
**so that** this dynamic behaviour ensures that users see only the options relevant to their department, improving both the usability and efficiency of the system.  
Similarly, if the user's department is "Marketing," the dropdown should show only values related to "Marketing," and so on.

<br>
