Relationships: One Upstream Item-Type has multiple different Downstream Item-Types

Iwan Kutter

Hello

I have a question regarding the best setup of the relationship between items.

Background: We have a big list with all features of our machines. This list contains everything belongs to the machine (and comes from an external system).

Based on this Feature list, we create downstream items of different Item types depending of the content (Design-, System- and Accessory Requirements).

At moment we set the Coverage flag in the Relationship setup to "No" for all item types. But then I cannot filter by missing Downstream in the Filter (or only manaully check with reports).

When I set it to Yes for all relationships, I get the issue that I need to link every feature to all 3 types that the relationship is fulfilled (and this will not be possible).
One workaround is to set the Coverage only for the most used type, but then I will miss the other types:

The rule I want to achieve is, that the coverage is fulfilled when one feature has at least one link to one of the sub-types. When there is no link, I have this in the filter for "Missing Downstream":

I see at moment only two solutions:

1. Split the list with Features into 3 types FeatureSystem, FeatureAccessory, FeatureDesign), But then I need to decide already on the list with feature, what type it is. The list is then also grouped into 3 different sections in the Explorer-Tree.
2. Combine the 3 Sub Item Types into one item type "Requirement" and add the a new pick list to this item with a sub type. But then I need to think every time when I want to add a relation between the sub types, in which direction I need to add the link.

Has anyone other ideas or some recommendation how to solve this? Or do you think this would something for a new ideation?

Thanks