Content
Updated by Eric Schubert 1 day ago
**As** an admin
**I want to** configure a custom field of type hierarchy to assign numeric values to the items
**so that** I can use that factor when calculating the result of custom fields of type calculated value.
**Acceptance criteria**
* When ~~When a creating a custom field, the user can now select a custom field of type "Factor list"
* A factor list hierarchy, the user must have be able to enable numerical values (factors) for the following configuration data: items.~~
* name ~~If factors are enabled, multi-selection cannot get enabled.~~
* required
* for all projects
* used as filter ~~If multi-selection is enabled, factors cannot get enabled.~~
* A factor list must not have ~~If factors are enabled, the following configuration data:
* multiselect
* An item of a factor list must have the following properties
* label - String
* factor - Float
* A user must be able to add enter a sub item to any item of a factor list.
### Hints and information
* factor lists are value, when editing or creating a different type than hierarchies, but they do use the same data structure below hierarchy item.~~
* "Hierarchy" will eventually be called only "List" and the old list will be considered deprecated. Those steps won't be taken in this feature. The future structure should be like this:
* We will have the type "List" and "Factor list"
* List items will have shorts, factor list items will have factors
* both will have a default value
* both will be able to add subitems UPDATE AC for new specifications (<mention class="mention" data-id="71476" data-type="user" data-text="@Eric Schubert">@Eric Schubert</mention> )
**I want to** configure a custom field of type hierarchy to assign numeric values to the items
**so that** I can use that factor when calculating the result of custom fields of type calculated value.
**Acceptance criteria**
* When
* A factor list
* name
* required
* for all projects
* used as filter
* A factor list must not have
* multiselect
* An item of a factor list must have the following properties
* label - String
* factor - Float
* A user must be able to add
### Hints and information
* factor lists are
* "Hierarchy" will eventually be called only "List" and the old list will be considered deprecated. Those steps won't be taken in this feature. The future structure should be like this:
* We will have the type "List" and "Factor list"
* List items will have shorts, factor list items will have factors
* both will have a default value
* both will be able to add subitems