Content
View differences
Updated by Niels Lindenthal over 1 year ago
As **Acceptance criteria**
* In Administration -> Project attributes a project portfolio manager
I want to set project values attributes of type hierarchy
So that I can more easily add structured information be created.
* In the project overview the attributes including values are shown.
* Hierarchy value selector for project list
* Current value picker for hierarchy values in work packages is not reusable
* It can be edited in the project overview (similar to a project portfolio in a single attributes of type list).
* Project list
* Filter
* Columns
* Sorting
* Journalizing
**Out of scope**
* Multi-step wizards which for entering the values step by step (e.g. Dezernat -> Amt ->Gruppe)
* Data migrations from separate project attributes
* Using the same custom field for projects and work packages (not globally activated).
* Administrator API to modify the hierarchy
* In Administration -> Project attributes
I want to set project values
So that I can more easily add structured information
* In the project overview the attributes including values are shown.
* Hierarchy value selector for project list
* Current value picker for hierarchy values in work packages is not reusable
* It can be edited in the project overview (similar
* Project list
* Filter
* Columns
* Sorting
* Journalizing
**Out of scope**
* Multi-step wizards which for entering the values step by step (e.g. Dezernat -> Amt ->Gruppe)
* Data migrations from separate project attributes
* Using the same custom
* Administrator API to modify the hierarchy