Fynn

Explain the problem as you see it

The existing grouping functionality is restricted to a single level or dimension, which results in a loss of valuable information during searches.

• A simple example works for a Kanban setup with a 'Status' dimension and a 'Assignee' dimension that normaly results in swimlanes.

• Another example are hierarchical structures that currently do not work at all, e.g. having either

• multi-level relationships within one supertag (parent-child) which would require more than just the proposed multi level / dimension grouping, i.e. defining parent-child relationships for 'instance of' fields

• multi-level grouping via multiple supertags / 'instance of' fields, e.g. my supertags are #Project and #WorkPackage and #Task and when doing my search for all my #Task nodes, I configure two grouping(levels) that would be the fields (currently we can only select fields for grouping sources) >related project and >related WorkPackage

Why is this a problem for you?

1. Limited Information in Searches:
Current searches provide less information than potentially available, especially in sophisticated setups.

2. Complex Workflows:
The current system complicates workflows by requiring users to jump between nodes and searches to navigate different levels of structure. This is cumbersome and obstructs the creation of information-dense visuals via searches

Suggest a solution

1. Multi-level Relationships within One Supertag:

• Implement parent-child relationships within a single supertag to enable hierarchical structuring.
• Example: In a #Task supertag, define parent tasks and subtasks to reflect a nested structure.

2. Multi-level Grouping via Multiple Supertags:

• Enable grouping by multiple supertags in searches.
• Example: When searching for #Task nodes, allow grouping first by >related project and then by >related WorkPackage.
• Provide interface options to easily select and configure these groupings.