Group by tags

[bryanwhiting]

Todoist has tags. They let you group all the tasks by tags. This would be very useful.

• Task 1 #projA
• Task 2 #projA
• Task 1 #projB

not done
group by tag 

Output:

ProjA:

• Task 1
• Task 2

ProjB:

• Task 1

[bryanwhiting]

Alternatively I can treat my headings as project labels and group by heading. But sometimes it's helpful to have multiple tags per task and to query them in a few places.

[AnnaKornfeldSimpson]

If you have multiple tags in a task, would you want to group on the whole set? Individual tags? And does the order matter?
For example, should - [ ] trim tree #personal #yard #daytime and - [ ] water flowers #personal #daytime #yard be in the same group(s)?
cc @MohamedBassem since I'm curious also for your thoughts on this re: #893
Thanks!
A fellow Tasks user who definitely needs to go handle some Tasks away from the computer screen... :)

[claremacrae]

Yes, I really want to do this.

I use tags like context/pc_clare, context/home, context/town... And in this case, I would really like the group headings to look like pc_clare, home, town.

At the moment I do this in my fork with a custom grouping command, group by context, but this obviously doesn't scale.

The original author of Tasks and I talked about this when I first implemented grouping.

From memory, we talked about having:

• group by tag - which would use the whole tag
• group by tag #context/ - which would only group by tags with that prefix, and strip off the prefix in the results...

One issue I haven't got my head around is what happens when there are multiple tags on a task. I guess the only sensible thing is to group by the first tag, if group by tag is used.

[bryanwhiting]

Per @AnnaKornfeldSimpson's question, I would agree with #893 that having the same task appear repeatedly (once for each associated tag) is the simplest solution.

• Task 1 #hello
• Task 2 #hello #world
• Task 3 #world
• Task 4

Would become

#hello

• Task 1
• Task 2 #world

#world

• Task 2 #hello
• Task 3

(Untagged)

• Task 4

Though I really like the idea of grouping by @AnnaKornfeldSimpson. So the result then would be

#hello #world

• Task 2

#hello

• Task 1

#world

• 3

Untagged

• Task 4

@claremacrae I love the idea of hiding the root for #context/tag and then grouping by subroot. I would think that if you had a mix of regular and nested tags it could be reasonable to extract the nest as a header?

[claremacrae]

Sorry, please do not go for anything that requires displaying tasks multiple times.

I want to focus on improving the current performance of tasks in large vaults, and have lots of stuff in my head around that at the moment.

Displaying tasks multiple times is too fundamental a change that I do not have the capacity to reason through all the consequences of right now.

[AnnaKornfeldSimpson]

@bryanwhiting I appreciate your generosity in calling my confusion/questions an idea! :) All credit to you for interpreting it. I think I was trying to figure out if (to use the tasks from your example above) a Task 5 #world #hello would be in the same group as Task 2. My initial thought is that yes it should be because remembering the right order for things is hard. Do you agree?

[claremacrae]

group by tags has been released, in Tasks 1.10.0.
See the docs.

[bryanwhiting]

Amazing!! Thank you for all the great work!!

[claremacrae]

Closing, as has been released.

[bryanwhiting]

💯💯💯💯💯 best reason to close an issue!!

[claremacrae]

As in, it was released in July last year, but GitHub have only recently added the ability to close Discussion tickets, so I’ve been doing some housekeeping. 😄