**Open question**: instead of introducing a new type, it would make sense to extend the custom field of type list to allow having a value associated with each list entry (think: enum instead of list). What needs to be done to make this happen? Adjust this description accordingly.

**Acceptance criteria**

* Begin of the insertiontheEnd of the insertion Begin of the deletion FactorEnd of the deletion list Begin of the insertionCF typeEnd of the insertion is Begin of the insertionmodifiedEnd of the insertion Begin of the deletion addedEnd of the deletion to Begin of the insertionallow each entry to have a numerical "factor" associated to its name

* "factors" and multi-select are mutually exclusive

* \[open\] hierarchical lists followEnd of the insertion the Begin of the insertionsame rules, so each entry might have a factor associated to its name

* the views for list CF types are adjusted to allow for entering factor values


<br>

**Acceptance criteria \[old\]**

* Factor list is addedEnd of the insertion Begin of the deletion availableEnd of the deletion as a project attribute

* The project attribute can be displayed in

* the project overview

* the project list

* A factor list has these details:

* Name

* Allow multi-select

* Required

* For all projects

* Used as a filter

* Searchable

* Factor lists have multiple values available in the values tab. There you can give a name to the value, define its factor and mark one as default.

* In the values tab, a search bar is present to be able to search attributes.

* There is a tab to activate this attribute in specific projects.