Content
View differences
Updated by Tobias Dillmann about 1 year ago
**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**
* Factor list is added to the available 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.
**Acceptance criteria**
* Factor list is added to the available 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.