⚡️ Ideas
Musa Musa Apr 5, 2023

Improvements to default behavior of "grouping" in search nodes

Explain the problem as you see it

Context:I created a search node to find tasks that I'm waiting for people to get back to me on, and I grouped the results by the "Assigned to" field.

  1. When you group by an option, the results are grouped according to the values that are "hit" by the search node at that moment. However, if you update or create new nodes that match that criteria with new values, they won't appear in the grouping unless you select the new values under "Group -> Show -> Select".

  2. When a previous value is no longer present in the search node, you have an those values still showing up

Why is this a problem for you?

  1. As I group the data by people, new values are frequently added, which requires me to check for any new additions in order to ensure that all results are displayed in the search node.

  2. As a result, the search results have many sort groupings that are currently irrelevant to me, making it difficult to find the information I need.

Suggest a solution

  1. Consider implementing default behavior for grouping search results or provide users with the option to "select all" when grouping.

  2. Consider grouping search results only by the current values for the relevant field that are returned by the search node. Additionally, if a hit drops off and it was the last value, dynamically remove the corresponding sort value to avoid irrelevant groupings.

⁨4⁩ ⁨Comments⁩

This issue makes grouping in search nodes useless for me, since I never know whether all the data is there. Each time I consult the search node I feel unsure and first have to review the list to check whether all groups have been activated.

? Deleted User May 21, 2023

Grouping is currently only useful for stuff like kanban boards where you have a couple of statuses that you choose pretty much once and that's it. Hopefully dynamic groups get implemented sooner than later.