When I give multiple tags to tasks it is easy to have a cluttered view of things in custom perspectives. The only partial solution is to group by “Tags (sorted),” but this makes for a very fragmented perspective with way too much information.
What I’d really like is to be able to only have a perspective include certain tags and just ignore the others.
For example, let’s say that I have two tags: a “Home” tag which indicates a context needed to complete the task, and “High Priority” to show its importance. I would ideally like to have two separate custom perspectives: one for ‘contexts’ and the other for ‘importance.’
Take the former for a moment (a custom perspective focusing on ‘context’). As things stand now, there’s no way to group by only those tags and not every tag a task with those tags also happens to have. I could list the task twice under separate “Home” and “High Priority” groupings and manually collapse the second. (However, if I created a counterpart perspective I would constantly be collapsing and expanding multiple tags because the settings are unhelpfully remembered across perspectives.) The only other option is to only list tasks once, but for each unique combinations of tags to have its listing. This is not very useful to quickly check what tasks I could accomplish at “Home” in a single list and hide distractions.
Again, what would be helpful is to create a perspective that lets me select certain tags to include (like my ‘contexts’) and to simply not group tasks based on other tags which would be irrelevant to that perspective. For this example, a perspective to just group by the tags which I explicitly include as part of the perspective and ignore any others.
The lack of this ability has prevented me from getting into a Forecast tag, because adding another common tag like that would kill the usability of several custom perspectives that are important to me in this way.
I hope I made this clear without going on too long. I believe Ken alluded to this sort of thing during the iOS TestFlight, but v3.1 has arrived and I hadn’t heard anything new.