New filtering system
- Edited
Jay Both of Jerud’s bugs are happening to me, FWIW.
For me, the not-hiding-completed only occurs if the completed item is a parent of at least 1 other non-completed item AND oddly if I have at some point since applying the filter clicked on the item to put it in edit mode. This happens whether I click the complete box while editing or after changing focus to another item.
I guess a key question is should children that are not marked complete but with a completed parent be shown in a -is:complete filtered pane? Goes to the inheritance issue, but common sense would suggest that they should be hidden. It looks like other exclude (or negated) filters hide children of an item that matches the exclude filter (so doesn’t pass the filter), even if any child item does not match the exclude filter (so does pass the filter).
- Edited
Tested some more with the filtering operators and definitely something is wrong with the operator logics
The filter: cereals and (“A ” or “B”) should be returning null as there are no entries with the word cereals and a word that ends in “A” or has"B",, however I am getting this result:
It’s bringing cereals as wella s items that end with A or have a B
- Edited
Fixed not hiding with children and the quotes + parentheses issue in the latest beta. How’s it looking now? I’m hoping that was the last of the bugs so we can release live soon 
. Please let me know if you find anything else!
It’s live! Thanks for all your help on this! We can of course keep improving it now, so please let me know if you find any more issues or have any more ideas. I’ll try to come back to some of the ideas I didn’t quite get to in the scope of this first release.
After the filtering system update, there was an error in the Korean input in the filtering box, making it completely impossible to use filtering (the consonants and vowels are separated and become multiple inputs). I’ve transferred all my data to Legend, and I can’t believe this is happening. I also sent more than five messages asking for Korean support, but there is still no feedback. Please solve this problem. If it’s impossible to solve, please tell me how to downgrade it. I sincerely ask for it.
- Edited
Good to see the release announcement, congratulations!
Btw., I added an “official” feature request to Filter on creation or modification dates - I think it would be really useful for many people.
- Edited
@Jay Found this Bug on Inputting more comprehensive filters
INputting this filter is almost impossible: -is:complete and “Project Manager” and -(#stepfuture or #steprejected )
I added the #stepfuture as the last item and it never allowed me to complete writing it Let me explain, I was able to completely write the #stepfuture in the filter field, and the contents of the pane seems to have correctly interpreted the criteria and altered the results accordingly. HOwever as soon as I clicked back on an item in the pane to work on it, the filter started changing deleting character by character the last few characters of the #stepfuture keyword, until only #step was left.
My hypothesis looking at the timing of the issue, that it might be a sync issue. I constantly have 2 or 3 instances of the windows desktop open AND the legend app running inside mailbird. I have always seen the lag between typing one thing in the windows desktop and a few seconds later seeing it reflected in the mailbird app (this is NOT a problem as it usually happens when you click away from the item you were adding). The lag is very similar to what I saw on the characters being deleted in my filter criteria.
When I closed the Legend application inside mailbird and tried again, typing the filtering criteria went in with no errors.
An additional error is an annoying consequence of the functionality that adds the tags in the filter to any new item that you create in the pane. With the filter above, Legend is not getting that I want to exclude the #stepfuture and #steprejected tags and because they are in the filter criteria, any new item I add gets added with those two tags, which a few seconds later (because they are filtered out) they disappear from the pane. This is not only confusing at first, annoying next but ultimately unproductive to have to switch to another view to be able to edit the stuff you just filtered for.
Jorge So it’s confirmed…. I have tried a couple of times to input more comprehensive filtering criteria with and without Legend app inside mailbird open and focused on the same pane, and whenever the mailbird app is open the bug shows up. If the mailbird app is closed then issue doesn’t materialize.
Legend’s ability to dynamically adjust items to match current filters does need work. It’s important for working in filtered Panes rather than merely viewing them.
Jorge’s example also appears to be a perfect illustration of how we actually need more “types” of tags. Many of us are having to use “structured” #tags to get multiple dimensions out of this single tool (in this case it looks like he’s applying ‘steps’ to items to track them through his process).
andrew Regarding auto-expanding the Overview, I think this has been discussed before but I think it becomes more noticeable when auto-expanding on any filter change…. since the Overview is not filtered, I don’t think it makes sense to auto-expand the Overview to match the expansion of the outline with a filter change. It ends up containing many entries that don’t match the filter. If the Overview were filtered (a separate debate!), it might make more sense to auto-expand it, but that is not the case.
@Jay I am bumping my previous post about the Overview pane being auto-expanded but not filtered because I think this really breaks the utility of the Overview. While I would prefer the Overview to be filtered, if it is not being filtered, it shouldn’t be auto-expanded, as it just ends up showing tons of irrelevant items and makes it fairly useless (at least for me).
- Edited
Jerud Yes me personally I am using the following prefixes to denote dimensions:
#at to denote geographic location
#cat to denote category of work
#step to denote kanban style teh current stage in a hiring process
#status to denote GTD style categories like Today, ThisWeek, NextWeek, Someday etc…
#pos to denote the title of a position i am interviewing someone for
#comp to dentoe a specific software component
andrew While I would prefer the Overview to be filtered, if it is not being filtered, it shouldn’t be auto-expanded
Me too. There are some other places I wish auto-expand didn’t happen as well; I find myself burning a lot of time “putting things back” just through the course of mundane work. This seems a personal choice though, maybe the solution is to just give users more control over the behaviors.
Jorge Yes me personally I am using the following prefixes to denote dimensions:
I’m only using three ‘dimensions’ but I have found it is critical for my mind to cope with the degree of complexity that I need to. Which is saying more about my mind’s limitations than the difficulty of the material! Legend works nicely so long as you only have 1 #tag; you can drag/drop between GB Tag Groups and Legend will intelligently remove the ‘source’ tag and replace it with the ‘destination’ tag. But if you have more than 1 #tag, Legend can’t know your intent so it simply appends the destination tag. It’s absolutely the “right” behavior…I’m just saying if there were different “types” of tag we could get more functionality and speed out of the app by eliminating that ambiguity.
My apologies for going a little tangential – but there was a reason: @Jorge’s “more comprehensive” filters could be simpler if more types of tag were available, and thus his observation of items vanishing from the filtered Pane would be that much easier to address.
BUG I just found today – the repro is kinda niche so maybe this isn’t new with the new filtering.
- Start with a ‘normal’ Pane – including the default “hide completes” filter.
- Switch to a GB Complete Date Pane. This forces completes to show (even though “hide completes” is still active).
- Switch back to any other Panetype. Completes will remain visible.
- Can be fixed by removing then reapplying “hide completes”.
Still finding some sneaky BUGS from this one @Jay
I have a Pane with advanced filter: -((is:bullet OR is:task) pri:low+) -is:project
This hides all items that have both a priority and are either a bullet or task. It makes a sweet Inbox Pane. But if I create a new item in that Pane, it appears with Pri:low pre-applied. I know that Panes will automatically apply properties to new items to prevent them automatically hiding – but that’s not needed in this case.
I’m guessing Legend is parsing the nested parentheses incorrectly.