Please consider making this bug a priority. I have discovered the same problem months ago, but assumed that it is by design. Unfortunately, this prevents filtering by the items that belong to a collection and therefore makes collections in practice quite unusable. For example, if you want to keep content organized inside collections also grouped by e.g. a project the content belongs to, that content will show up outside a collection as well for any views filtering by project.
We are rebuilding/upgrading our Collections system (as seen here). Although I’m not entirely clear on your use case for Collections today, if you could see the new implementation and check if it suits your needs, that’d be good. Currently, backlinks are used primarily for linking across objects, not necessarily as a way to reference which collection it belongs to.
Thank you for your reply. I noticed that post, and I’m looking forward to the new design.
Could you please confirm that currently it is simply not possible to create a filter (in a view such as a list) that would filter objects based on whether they belong to a collection or not?
Dear @kaye , but as @czikus already asked, it must be possible to filter a Querie’s View for Objects that aren’t connected to a Collection!
That is (and was always) an often used feature; I can’t believe that the team is about to remove this option!?!
I’ve reported it as a bug on 20. February and there was some discussion with Filip about it. Seems he didn’t know about it and no other team member has given an answer.
I was in hope all the time that it soon becomes fixed …
