Feature: A Table Grouping Mechanics - Groups shouldn't be mutually exclusive

Currently Table Groupings on Select Column treat each combination as a unique set, this is problematic especially for task management.

For example:

  • Task A is assigned to Person A
  • Task B is assigned to Person B and Person A

When I group the task table by assigned person, Task B does not show under Person A but only Person A + Person B. This is very confusing for Person A because Person A now has to go look for all groups containing Person A. As such, every person has to do additional steps of filtering the table.

I suggest an option to allow all rows (e.g. Tasks) that contains a select value (e.g. Person) to also fall under the single select value’s group (e.g. Task B, that was assigned to Person A and Person B, to show up under Person A’s group)

Hello @Jireh_Chan ,

I understand the limitation you experience with grouping, but I don’t think the Coda team is going to solve this for you (I am pretty sure it is intentional it works this way).

Therefore, I would approach this not by grouping the task table, but by having a task column in the assignee table (your team, employees or staff). There can be a lof of finetuning (you could show a view filtering out employees without any tasks), you can show only the task name or (in a modal) show a table view of the task (open an assignee record to see what that looks like), you can restict editing the task, etc. etc.

Check the sample doc: