Content
View differences
Updated by Niels Lindenthal over 1 year ago
In some scenarios, users are required to manage complex information that naturally fits into a hierarchical structure. e.g.
* Real Estate: Property -> Buildings -> Floors -> Rooms
* Geographical Data: Continent -> Country -> Federal State -> County
* Organizational Structures: Organization -> Department -> Team -> User
* Product Components: Parts list of a machine
Currently, only flat lists are available. Flat lists can be challenging in managing and navigating through this information. Without a hierarchical view, it becomes difficult to maintain, locate, and work with these datasets effectively.
This avoids the following pain points:
* Users, particularly project managers and project members, need a way to save and organize information in work packages using hierarchical structures.
* A hierarchical representation would allow them to focus on relevant subsets of information, making navigation more intuitive and information retrieval easier.
* Real Estate: Property -> Buildings -> Floors -> Rooms
* Geographical Data: Continent -> Country -> Federal State -> County
* Organizational Structures: Organization -> Department -> Team -> User
* Product Components: Parts list of a machine
Currently, only flat lists are available. Flat lists can be challenging in managing and navigating through this information. Without a hierarchical view, it becomes difficult to maintain, locate, and work with these datasets effectively.
This avoids the following pain points:
* Users, particularly project managers and project members, need a way to save and organize information in work packages using hierarchical structures.
* A hierarchical representation would allow them to focus on relevant subsets of information, making navigation more intuitive and information retrieval easier.