Old baselined requirements appear in coverage and traceability matrix

Old baselined requirement appears in coverage and traceability matrix. Only current version shall appears in in coverage and traceability matrix
see exemple in attached file. JUSTIF_BUBBLE_027 and JUSTIF_BUBBLE_027 v29 covers the requirement SyRS_BUBBLE_001.
Even if we delete the baseline corresponding to JUSTIF_BUBBLE_027 v29, this requirement stays in coverage and traceability matrix.

Coverage matrix is also impacted

How to reproduce

• Create 2 pages with requirements with a dependency,

• Create a baseline for the page with the dependency, so that the baseline contains one requirement but not the other,

• Reindex the other page (or edit it),

• A dependency will be visible from the "current" to the "baselined" requirement.

Root cause

• When we create the baseline, we copy the dependency from the baselined requirement to the requirement outside the baseline;

• When we reindex, the algorithm stumbles upon the requirement with seemingly a missing link, and "restore" the other side of the link, thus creating this extraneous link.

Resolution

We'll add a condition in the indexation, to avoid recreating links when we are the "destination", current version, and the other side is a baselined version.

We'll also create an upgrade task to delete all dependency links, on the "DESTINATION" side, where the requirement is current and the other side is baselined.