Old baselined requirements appear in coverage and traceability matrix

Description

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.

Environment

None

Observations

None

Activity

Show:
Adrien Ragot (Play SQL / Requirement Yogi)
March 6, 2020, 1:59 PM

Hi Alexandre,

I have just published RY 2.4.6, which fixes your issue.

It runs a background upgrade task to fix existing relationships, so it make take an hour after the installation to delete the extraneous data. When ready, the task named "Requirement Yogi: Soft upgrade tasks" removes itself from the Scheduled Job in the Confluence administration.

Best regards,
Adrien Ragot

Adrien Ragot (Play SQL / Requirement Yogi)
March 3, 2020, 3:31 PM

Hi Alexandre,

I have succeeded to reproduce the conditions for this bug.

It will be solved in the next release.

Best regards,
Adrien Ragot

Adrien Ragot (Play SQL / Requirement Yogi)
March 2, 2020, 5:28 PM

Hi Alexandre,

I am having difficulty reproducing your data. Do you know in which circumstances you were able to create a dependency in that direction, from BR_RD2I_001 to PR_RD2I_003?

Apart from this, I will hide such relationships in the next release, unless the "Show all versions" flag at the top-right of the matrix is enabled.

Thank you for this report,
Adrien

Resolved

Assignee

Adrien Ragot (Play SQL / Requirement Yogi)

Reporter

alexandre.liaut

Labels

None

Participants

None

Components

Fix versions

Affects versions

Priority

Matter of days