Questions about aggregator swimlane behavior

[maybe-hello-world]

I'm trying to understand the aggregator swimlane behavior and would appreciate the explanation.

I've created a sample vault with just a couple of tasks:

When I'm creating swimlanes based on tags, I'm not sure I understand the behavior of the aggregator swimlane. Assuming I created a swimlane for "tag2" and enabled the aggregator swimlane, I receive the expected outcome - empty swimlane for "tag2" and all other tasks in "other":

However, if I create a swimlane for "tag1" instead of "tag2", I will see a swimlane for "tag1" with one task and no aggregator swimlane:

How does the aggregator swimlane decide whether to appear or not? Am I using it incorrectly (expecting in this swimlane just everything that doesn't fit in other swimlanes, including lack of tags)? If yes, is there a way to specify "no tags" swimlane for tag-based swimlanes?

My goal is to create swimlanes for some projects based on tags, and let all other tag- or tagless- tasks to live in the "aggregator" swimlane but it disappears resulting in tagless tasks not shown on the board at all.

[maybe-hello-world]

Ah, I believe I found the reason - seems like aggregator swimlane is shown if in this swimlane there will be at least 1 item with a tag - in this case both items with tag and without tag will be shown. If only items without tag belong to the aggregator swimlane, it will not be shown. Not sure if it's intended behavior or a bug.

[tu2-atmanand]

Hi @maybe-hello-world !

Thank you for reporting this issue.
I just tested this and found that, its actually a bug.

In the second case, the "Aggregator swimlane" (All rest) should render itself with the "task2".

The only criteria for "Aggregator swimlane" to be shown is that, atleast one of the column inside the swimlane should have atleast one task in them. In your example, since the "Backlog" column have one task and which is supposed to be shown inside the "Aggregator swimlane", hence this last swimlane should have been visible. But, looks like, because of some bug, the "Aggregator swimlane" is failing to render.

Will fix this issue soon. Created a ticket to track its development : #779

[tu2-atmanand]

The bug has been fixed. Please refer this comment : #779 (comment)