Content
View differences
Updated by Marc Alcobé almost 2 years ago
**As** an OpenProject user
**I want to** have custom fields of type "Hierarchies"
**so that** I can more easily specify and filter based on those hierarchical attributes.
**Examples:**
* Property -> Buildings -> Floors -> Rooms
* Continent -> Country -> Federal state -> County
* Organizations -> Department -> Team -> User
* Parts list of a machine
* OpenProject module
**Acceptance criteria**
* When ever we work with the hierarchy, it is not necessary to load the full hierarchy as hierarchies can easily bigger than 1k elements.
* Administration
* create such an attribute
* set to single- or multi-select
* create nodes one by one
* modify parent
* delete node
* rename node
* provide acronym per node
* Interface for non admin, e.g. in a work package form
* A selected value can have multiple value representation
* Node ID
* Full path long: Europe -> Germany -> Bavaria
* Full path short: EU-DE-BY
* Selected long: Bavaria
* Selected short: BY
* Selection
* Select a leaf (e.g. Bavaria)
* Select a node (e.g. Germany)
* Allow multi-selection
* Filters
* By node or leaf (e.g. Bavaria only, Germany only)
* By node with descendants (e.g. Germany, including all federal states)
**Out of scope**
* Manual sort order. So for the time being elements are sorted alphabetically per node.
* Multiple changes to the hierarchy get saved in one transaction instead of multiple ones.
* Allow the same custom field to be active on work packages AND projects, or any other entity type we allow custom fields for.
**Figma and visuals**
https://www.figma.com/design/oTMDTvcwrx35qExTkkSKBn/Custom-fields?node-id=386-8676 https://www.figma.com/file/oTMDTvcwrx35qExTkkSKBn/Custom-fields?type=design&node-id=386-8676&mode=design
**I want to** have custom fields of type "Hierarchies"
**so that** I can more easily specify and filter based on those hierarchical attributes.
**Examples:**
* Property -> Buildings -> Floors -> Rooms
* Continent -> Country -> Federal state -> County
* Organizations -> Department -> Team -> User
* Parts list of a machine
* OpenProject module
**Acceptance criteria**
* When ever we work with the hierarchy, it is not necessary to load the full hierarchy as hierarchies can easily bigger than 1k elements.
* Administration
* create such an attribute
* set to single- or multi-select
* create nodes one by one
* modify parent
* delete node
* rename node
* provide acronym per node
* A selected value can have multiple value representation
* Node ID
* Full path long: Europe -> Germany -> Bavaria
* Full path short: EU-DE-BY
* Selected long: Bavaria
* Selected short: BY
* Selection
* Select a leaf (e.g. Bavaria)
* Select a node (e.g. Germany)
* Allow multi-selection
* Filters
* By node or leaf (e.g. Bavaria only, Germany only)
* By node with descendants (e.g. Germany, including all federal states)
**Out of scope**
* Manual sort order. So for the time being elements are sorted alphabetically per node.
* Multiple changes to the hierarchy get saved in one transaction instead of multiple ones.
* Allow the same custom field to be active on work packages AND projects, or any other entity type we allow custom fields for.
**Figma and visuals**
https://www.figma.com/design/oTMDTvcwrx35qExTkkSKBn/Custom-fields?node-id=386-8676