+1 for adding Object Type (relation) as an option in Group By menu in Kanban view.
Any good reason why Kanban Group By options are limited to Tag and Checkbox relation types? Why are we able to filter and sort within Sets and Collections with Object Type but can’t Group a Kanban by it?
Hello, I don’t know if this feature request is still “up to date”, but I am also super interested in it. One of my uses of Anytype is to outline novels. I have the objects Scene and Chapter (one Scene has one Chapter, a Chapter can have multiple Scenes). For now, in my Scene object, I have a relation to the Chapter object, but also to use the Kanban view I have a select element that takes the name of the Chapter. Like OP in their first few screenshots, I have to duplicate the information with one “object” and one “select” relation. This is not great to maintain and I would love to be able to use an object field to “group by” in Kanban.
I am using other apps that allow this, and their solution is usually that when you create a relation (in my case, the relation to Chapter from my object Scene), you decide if in this “object” field you can add one or multiple elements. I understand that multiple elements in one field can’t work with Kanban, but if we could create relations that contain only one object, then I suppose the problem could be solved.
So far I have almost completely migrated my writing system to Anytype, but grouping in queries is the last thing that makes me come back to another software for bigger projects. I would be more than happy to give more info on my setup or clarify my example if needed, and even happier to fully migrate my projects to Anytype
Giving this a bump as it would be great to have. My use case is for a query that collects everything with a given tag. I’d love to be able to see my “Bookmarks” in one column and my “Notes” in another to separate things by object type.