Merge or “Consolidate” Extended Relations is Collection Views and Boards

Another great feature of Fibery are the powerful, multi-directional Lookups. I frequently use these to “extend” deep across multi-level Relations, to get to the same entity that can be related directly to another entity, but also be visible through an extended LookUp many levels and directions away.

One thing I’ve found is that I when I create these set ups, I get the relation showing up from the particular connection in many “Collections.” Here’s what I mean:

In the Fibery Product Team Template, we have a Product Area that can relate to both a Feature and a Story. However, a Story is also a child to a Feature. If we want to see on the Product Area’s Collections the Stories that are not directly related, but are part of a Feature, we have to set up a LookUp from Features. This will be called something like “Features’ Stories.” However, we have another Collections area showing the directly related Stories. So in the end, we have two sets of Story Collections, but in reality all those Stories are “connected” to the Product Area.

So I think it would be great if we could consolidate when we create extended connections to the same Type, without having multiple Collections that are in isolation from each other, even though they are about the same Type.

This would also be very helpful in Boards, because as I understand it, the common Type would be available as a Row or Column. So in this example, you could make a board with “Tasks” as the Entity represented, and “Product Area” as a row. And then you could see all Tasks associated with the Product Area, including those not directly related but part of Features.

Thanks and hope that’s clear!

1 Like

I understand the need you’re describing, but I think it’s worth noting that on some occasions the distinction between the two relations is important, and it is not desirable to aggregate them. For that reason, if ‘consolidation’ was available, then it needs to be optional.


Chris, 100% yes. I should have actually mentioned that, so thanks for adding. No question I would like to have both cases:

  • Where I can show distinct instances of the a relation or Lookup to the same Type

  • Where I could consolidate into one “aggregate” collection of Entities out of the Type that is related in multiple ways - directly, via Lookups.

Thanks again!