Content
View differences
Updated by Eric Schubert over 1 year ago
**As** a user \[enter role of user\]
**I want to** add items from a custom field hierarchy as a value to the work package \[enter objective\]
**so that** I can select the \[enter desired state for my work package. result\]
**Acceptance criteria**
* A instance admin must be able to add a custom field of type hierarchy to the form configuration of a work package type.
* A project admin must be able to activate a custom field of type hierarchy inside a project.
* A user must be able to select one (no multi-select) or many (with multi-select) items from the hierarchy to assign them to the work package.
**Trivia**
* Focus is still on work package custom fields.
* Work package view is angular
* we use the ng-select component first (drill down selector is not ready yet)
* we need at least some api access to fetch the needed data
* Does rendering the custom field value impacts heavily the load of the work package? Investigate!
**I want to** add items from a custom field hierarchy as a value to the work package
**so that** I can select the
**Acceptance criteria**
* A instance admin must be able to add a custom field of type hierarchy to the form configuration of a work package type.
* A project admin must be able to activate a custom field of type hierarchy inside a project.
* A user must be able to select one (no multi-select) or many (with multi-select) items from the hierarchy to assign them to the work package.
**Trivia**
* Focus is still on work package custom fields.
* Work package view is angular
* we use the ng-select component first (drill down selector is not ready yet)
* we need at least some api access to fetch the needed data
* Does rendering the custom field value impacts heavily the load of the work package? Investigate!