# Epic FND-8 - Cascading work package custom fields / conditionally display custom fields

Project: Stream workspace foundations
Status: new
URL: https://community.openproject.org/work_packages/FND-8

## Detailed specification

### Motivation and background information

Currently, there is no native support for cascading logic between fields - where the value, visibility, or available options of one field are driven by the value of another.

### Acceptance criteria

Enable administrators to define cascading relationships between fields (incl. custom fields) so that selecting a value in one field dynamically filters the allowed values in dependent fields during work package creation and editing.

*   Cascading allowed values: The options available in Field B are filtered based on the selected value in Field A
    
*   Support for multi-level cascades (A → B → C)
    
*   Admin UI to define and manage cascading relationships between custom fields
    
*   Behavior applies during work package creation and editing
    
*   Cascades should be also available while defining contextual fields (if these are available at the point of implementation of this work package)

### Out of scope

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

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q2 |
| Date |  |
| Votes | 14 |
| List |  |
| Target versions | Wish List |
| 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 |  |
| Accountable |  |
| Product manager | Sonita Soth |
| Designer | Parimal Satyal |
| Developers | OP Dev Comms Team |
| Requested by |  |
| Interest by | Bowling (40324) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | 80d 0h |

## Description

1.  As an **administrator**, I want to define a cascading relationship between two custom fields so that the options in the dependent field are automatically filtered by the value chosen in the parent field.
    
2.  As an **administrator**, I want to chain multiple cascading fields so that a three-level hierarchy (e.g. Domain → Service Category → Service Item) is enforceable in a single form.
    
3.  As a **requestor**, I want dependent fields to show only valid options based on my prior selections so that I cannot submit an invalid combination.