Traceability Matrix - Error 500 - DependencyDAO assumes the same spaceKey / baseline

Fix versions

Priority

Description

Symptom: The traceability matrix displays an error 500

Steps to reproduce: Link a requirement to a baseline requirement and display it in traceability matrix.

Root cause

Due to past optimization, we assumed a method could only work on requirements with the same space key / baseline, but we’ve factorized all the code into a few methods, and now others can call this method.

Solution

It was a programming error, we’ve extended the function to work on several keys / space keys.

Workaround

Data from several spaces / baselines couldn’t be mixed in some areas of the treacebility matrix, so one solution is to try to only work on non-baselined requirements, in a single space (which is impossible if there are cross-space requirements).

Attachments

1

Activity

Show:
Resolved

Details

Assignee

Reporter

Sprint

Release date

Requirement Yogi

Created February 27, 2025 at 7:43 AM
Updated February 27, 2025 at 2:35 PM
Resolved February 27, 2025 at 1:48 PM