I was really hoping the new “group by” option would potentially solve this, but at least in it’s current experimental form, it’s not particularly useful for me.
There’s at least 4 solutions to the same issue, and I would accept any of them:
Option 1 (Ideal Solution):
If a context filter is applied to the “All Databases” tab, automatically apply the same filter across every level in the hierarchy.
Option 4:
Allow multiple levels of “grouping”, so the context filter can be applied to the lower level and all other levels are just “groups” that inherit their context from the entity at the bottom.
To be fair, that use case is covered, since Assigned to me can be used at any level.
But if you mean a context view where the Project and its Tasks is filtered for a specific user, then indeed, it is an example of context filtering at multiple levels.
So I recently had to change the way certain databases were related (from M-M to 1-M) and now I need this feature more than ever since I can no longer even manually apply the desired filter once at the “All Databases” level and instead have to apply it manually on every single level, every single time.
I was optimistic that the grouping feature might help but, it turned out to be largely useless (for my use case at least) because groups don’t respect the context filter of the things within them, and context filters can’t be applied to groups!
Is there really no workarounds out there to dynamically/contextually filter multiple levels?
I’m sure it’s not easy at it seems to implement, but it feels like a huge missing feature when one of Fibery’s core pillars is “contextual data”.
