And in filter with outline view shows wrong items

wilhelmmedetz

Collapse mathes of filters: On

Sample List

List view - filter for #t1 #t3

matches correctly item a

Outline view - filter for #t1 #t3

shows subitems of item a, although none of these items matches the filetr #t1 and #t3

LauraH

This is not a bug. Though you are not the first to be confused by this behavior.

The way Legend filters currently work in OUTLINE view is that once an item in the tree matches the filter, that item AND ALL OF IT’S CHILDREN are shown. (As you rightly note - LIST view is what to use if you want to see only the individual matching items.). So, the behavior here is the expected behavior. Since “a” matches the filter, “a” and all it’s children are shown.

I personally use this aspect of legend all the time. I LIKE that Outline view shows all children of a matching item, and i use that as part of my workflow on a regular basis. (For example: I can add a “#Q1” tag to a PROJECT for this quarter, and searching for that tag in outline view lets me see and edit the entire project, without having to tag every individual item in the project. )

wilhelmmedetz

LauraH The problem is I have set ‚Collapse matches of filters: On‘.
In this case children of an item should only be shown if any of the children matches the filter.
In my sample none of the children matches ˋ#t1 #t3ˋ (meaning #t1 AND #t3).
Thus I believe this is a bug.

Jeff

wilhelmmedetz LauraH is correct that this is not a bug, but expected behaviour in Legend.

In outline view, filters with multiple “and” terms consider the ancestors of an item, up to but not including the item that is currently zoomed to, to determine a match. That’s described briefly in the “Filter” section of the help document, have you seen that?

In your example, ‘c’ has the #t3 tag, and has an ancestor ‘a’ with a #t1 tag, so it matches the filter. Thus ‘a’ is not collapsed, because it has a matching child.

Something not explained in the help is that it’s only the deepest item, the “this” item in the example, that’s actually a match, in the sense that all of its non-excluded descendants will be displayed (though possibly collapsed), while if the “filter” item had other non-matching children, they would be hidden. On the other hand, the status bar will show both as “items matching the filter”. If we start with this:

Then, with “collapse matches” on, we get:

The “this” item is a match, because it has “this”, and an ancestor with “filter”. The “and that” item is not hidden, because all non-excluded descendants of matching items are displayed. But “this” is collapsed because “and that” doesn’t match. On the other hand, “and that” is included in the total of 3 “items matching filter” in the status bar. Meanwhile, “not the other” his completely hidden, and not included in the “items matching filter” total. That’s because its parent, the “filter” item, is not a matching item - even though it is also included in the total of “items matching filter”. It seems there are some holes in the help documentation, and inconsistencies with the terminology within Legend, which can be confusing to new users. That’s partly because the filters were quite recently renovated, including the addition of the “collapse matches” setting. But the actual behaviour is basically as expected.

LauraH is also correct that in list view, only individual items matching all the filter terms will be shown, in other words, it doesn’t work across the hierarchy. That’s also not explained in the help document. But, as you know, it has disadvantages, like that you can’t see the descendants if you want to. Some people have suggested that there should be a way in outline view to constrain “and” matches to individual items, while still showing the hierarchy of those that match. So far there hasn’t been any agreement for how that would work in the user interface. You’re welcome to create a feature request, and describe how you see it working.