Skip Navigation LinksHome Page > Forums > SpiraTeam Forums > Spira Custom Reports > Out of the box tracebilit...
I am trying to understand a logic of a default (out of the box) "Requirements Traceability" report. Could you provide a sql logic that is under it? Especially I am interested what requirements are shown in it's "Requirements Traceability" column.
The report doesn't use Entity SQL to generate its data, it is using the same code that is used to generate the requirements hierarchical list page: https://spiradoc.inflectra.com/Spira-User-Manual/Requirements-Management/#requirements-list
It uses the same filtering methodology that is used on that page for the left-hand column.