# User Problem

## User

* Project manager

* Project member

* Administrator


## Problem

Begin of the insertionIn some scenarios,End of the insertion Begin of the deletion * At times,End of the deletion users Begin of the insertionare requiredEnd of the insertion Begin of the deletion needEnd of the deletion to Begin of the insertionmanage complexEnd of the insertion Begin of the deletion deal withEnd of the deletion information that Begin of the insertionnaturally fits intoEnd of the insertion Begin of the deletion is best displayed as hierarchy. 

* Users want to save this information in work packages.

* At the moment only flat lists are available.

* Here are some examples of data that would be best shown withinEnd of the deletion a Begin of the insertionhierarchical structure.End of the insertion Begin of the deletion hierarchyEnd of the deletion e.g. Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the insertion**Real Estate:**End of the insertion Property -> Buildings -> Floors -> Rooms Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the insertion**Geographical Data:**End of the insertion Continent -> Country -> Federal Begin of the insertionStateEnd of the insertion Begin of the deletion stateEnd of the deletion -> County Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the insertion**Organizational Structures:** OrganizationEnd of the insertion Begin of the deletion OrganizationsEnd of the deletion -> Department -> Team -> User Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the insertion**Product Components:**End of the insertion Parts list of a machine Begin of the insertion


Currently, only flat lists are available. Lists can be challenging in managing and navigating through this information. WithoutEnd of the insertion Begin of the deletion

* The advantages ofEnd of the deletion a Begin of the insertionhierarchical view, it becomes difficult to maintain, locate, and work with these datasets effectively.

## Pain

End of the insertion Begin of the deletion hierarchic list are:

End of the deletion * Begin of the insertionUsers, particularly project managers and project members, need a wayEnd of the insertion Begin of the deletion Makes it easierEnd of the deletion to Begin of the insertionsave and organize information in work packages using hierarchical structures.

End of the insertion Begin of the deletion locate specific items.

End of the deletion * Begin of the insertionA hierarchical representation would allow them toEnd of the insertion Begin of the deletion Users canEnd of the deletion focus on relevant subsets of Begin of the insertioninformation, making navigationEnd of the insertion Begin of the deletion information.

* Drill-Down Navigation: Users can navigate through different levels of the hierarchy, which can make the UI feelEnd of the deletion more intuitive and Begin of the insertioninformation retrieval easier.End of the insertion Begin of the deletion structured.


## Pain

* Hierarchies are not possible at the moment, only flat lists can be used.

* This makes it complicated to maintain, find and select values.End of the deletion


# Business Case

## Begin of the insertionSolutionEnd of the insertion Begin of the deletion ReachEnd of the deletion

Begin of the insertionThe solution involves implementing aEnd of the insertion Begin of the deletion > Add this value to theEnd of the deletion custom field Begin of the insertionof type "hierarchy"End of the insertion Begin of the deletion and delete this section.

## Impact

> Add this valueEnd of the deletion to Begin of the insertionallow usersEnd of the insertion Begin of the deletion the custom field and delete this section.

## Confidence

> Add this valueEnd of the deletion to Begin of the insertionmanageEnd of the insertion Begin of the deletion the custom fieldEnd of the deletion and Begin of the insertionnavigate information in a structured, multi-level formatEnd of the insertion Begin of the deletion delete this section.End of the deletion

Begin of the deletion ## Urgency and Priority

> Add this value to the custom field and delete this section.

## Solution

End of the deletion ### Summary

* The Begin of the deletion solution is a custom field of type hierarchy.

* TheEnd of the deletion admin needs to be able Begin of the insertionto 

* Create aEnd of the insertion Begin of the deletion to create thisEnd of the deletion custom field Begin of the insertionof type "hierarchy" (onEnd of the insertion Begin of the deletion and set values onEnd of the deletion admin Begin of the insertionlevel)

End of the insertion Begin of the deletion level.

End of the deletion * Begin of the insertionSet values (on admin level)

End of the insertion Begin of the deletion Project admins need to be able to enable / disable this custom field on project level.

End of the deletion * Nodes should be able to have Begin of the insertionoptionally an abbreviationEnd of the insertion Begin of the deletion short and long form for displaying information in shortEnd of the deletion e.g. Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Headquarters Begin of the insertion->End of the insertion Begin of the deletion > LevelEnd of the deletion 1 Begin of the insertionFloorEnd of the insertion -> Room 2 Begin of the insertion**in short:** "HQEnd of the insertion Begin of the deletion => HQEnd of the deletion -> Begin of the insertion1FEnd of the insertion Begin of the deletion Lvl 1End of the deletion -> Begin of the insertion2"

End of the insertion Begin of the deletion Room 2

End of the deletion * Europe -> Germany -> Bavaria -> Weißenburg Begin of the insertion**in short:** "EUEnd of the insertion Begin of the deletion => EUEnd of the deletion -> DE -> BY -> Begin of the insertionWUG"

* Project admins need to be able to

* enable / disable this custom field on project level.End of the insertion Begin of the deletion WUGEnd of the deletion

* Other custom fields Begin of the insertionshouldEnd of the insertion Begin of the deletion needEnd of the deletion to be able to access the value of the selected item from the custom field of type hierarchy.

* It should be also possible to access partial information e.g. the parent Begin of the insertionnode,End of the insertion Begin of the deletion node andEnd of the deletion short Begin of the insertionandEnd of the insertion Begin of the deletion vs.End of the deletion long form of a value


### Begin of the insertion

###End of the insertion Admin Interface

* Create nodes

* Set parent (and be able to change parent afterwards)

* Validations / Services / Contracts

* Data structures

* Path / Breadcrumb

* Long form

* short form


### API

* Add to work package representer

* Query

* on work packages (start with this one)

* on users

* on groups

* on projects

* Filter on

* Operators

* all assigned to a certain node

* all assigned to a certain node and its descendents

* Allowed values

* Group by

* WP/project/users/groups form

* link to typeahead backend

* Values endpoint

* Typeahead for value searching

* drill down

* get all children for node

* get all as tree (needed for quick solution with ng-select)

* Documentation


### Angular Frontend

* Render values

* In WP full view

* In WP table column

* Select values

* ng-select based (browsing the hierarchy)

* single select

* multi select

* search on path (typeahead) (searching the hierarchy, )


### **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 for Begin of the deletion theEnd of the deletion iteration 1

* Drill down selector. Begin of the insertionA componentEnd of the insertion Begin of the deletion It'sEnd of the deletion like a location/file Begin of the insertionpicker. TheEnd of the insertion Begin of the deletion picker where theEnd of the deletion user can click on nodes Begin of the deletion (instead of folders)End of the deletion to Begin of the insertiongo one level deeper onEnd of the insertion Begin of the deletion findEnd of the deletion the Begin of the insertionhierarchy.End of the insertion Begin of the deletion item. This is needed to for selecting an item within a large amounts of hierarchical items (Needs clarification what drill down pattern would be the most accepted by users Folder-Style vs. Tree +)End of the deletion

* Manual sort order. Begin of the insertionForEnd of the insertion Begin of the deletion So forEnd of the deletion 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.


##

## Next iteration

* The next iteration would be extending the Begin of the insertionhierarchicalEnd of the insertion Begin of the deletion hierachicalEnd of the deletion custom field with a drill down selector. Begin of the deletion

* Drill down selector. It's like a location/file picker where the user can click on nodes (instead of folders) to find the item.End of the deletion This is needed Begin of the deletion toEnd of the deletion for selecting an item within a large amounts of hierarchical Begin of the insertionitems. This needs clarification what drill down pattern would be the most accepted by users Folder-Style vs. a small + button on a tree structure


End of the insertion Begin of the deletion items


End of the deletion # Launch and Growth

## Measures

* Begin of the insertion tbd


End of the insertion Begin of the deletion


End of the deletion ## Messaging

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Headline</p></th><td class="op-uc-table--cell"><p Begin of the insertionclass="op-uc-p">Custom fields of type Hierarchy makes project managers and members life easier.</p></td></tr><trEnd of the insertion Begin of the deletion class="op-uc-p">Hierarchical attributes for work packages.</p></td></tr><trEnd of the deletion class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">First Paragraph</p></th><td class="op-uc-table--cell"><p Begin of the insertionclass="op-uc-p">A hierarchical representation of data makes navigation more intuitive and information retrieval easier. For data that don't fit intoEnd of the insertion Begin of the deletion class="op-uc-p">LikeEnd of the deletion a Begin of the insertion<s>box</s> flat list.&nbsp;</p></td></tr><trEnd of the insertion Begin of the deletion list but structured.</p></td></tr><trEnd of the deletion class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Customer Quote</p></th><td class="op-uc-table--cell"><p Begin of the insertionclass="op-uc-p">It's needed for our ...</p></td></tr></tbody></table></figure>End of the insertion Begin of the deletion class="op-uc-p">We need this.</p></td></tr></tbody></table></figure>End of the deletion

## Go to market

**Figma and visuals**

https://www.figma.com/design/oTMDTvcwrx35qExTkkSKBn/Custom-fields?node-id=386-8676