Comment #⁨4⁩

There are at least a couple of reasons that I prefer the solution that uses grouping quite independently of whether Tana should allow users to drag and drop between search nodes:

  1. In cards view you can use the multiple column display that Tana already has. I strongly suspect that users who use this task organisation workflow would prefer to be able to organise tasks in this Kanban-style manner, and this takes advantage of something that is already provided by Tana. Trying to achieve something similar with search nodes would require opening them into separate panels, and given that it is likely that this would require four or five panels to be simultaneously open some user simply will not have screen real estate for this.

  2. This provides a built-in solution for a common use case, and does not require that less technical users manually create the required search nodes.

The question of whether Tana should allow users to drag-and-drop between arbitrary search nodes is one that ultimately Tana must answer. I see numerous difficulties there.