I had the following structure: Product -> Capability.
I had to introduce another level named “Capability Area” in the middle so that the structure becomes: Product -> Capability Area -> Capability. In order to do that, I renamed the existing “Capability” type to “Capability Area”.
Then I added a new type named Capability under Capability Area, thereby achieving Product -> Capability Area -> Capability.
For a productive board view to manipulate the relations, I need the Capabilities as cards, Products as columns and Capability Areas as rows. For this, I need a relationship from Product to Capabilities directly, too*. But the problem is now I can’t create a simple relation from Product to Capability entity or vice versa as seen in the screenshot below:
I have a hunch that this is being caused due to the system getting confused because of the old “Capability” type that was later renamed to “Capability Area” - I had seen such stale type names in the exported JSON in general (but didn’t analyze further for this case).
*BTW, this is an example where “Extended or Derived” relationship concept could otherwise help and not require explicit relations beween all levels in a relationship hierarchy or chain.