Content
View differences
Updated by Rosanna Sibora about 13 hours ago
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)
* 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)