Below are the steps to recreate this problem: - 1) Set the default option for link constraints (' transfer to child' for both primary and secondary links); 2) Link two requirements;
Cardinality constraint: 1:n (i.e. a BR can only be linked with one single Rel) Transfer Link to child (both checkboxes ticked) (i.e. link will be transferred to child of BR as well as to child of Rel when replaced) Scenario:
If you create a new version of a requirement using Replace and then delete that new version, you may still see the new (deleted) version of the requirement as part of the collection. This can happen if you selected " Transfer to parent on deletion of child" as one of the parameters when you created the collection.
