Recently, our QA/regulatory decided to run an audit and they requested a traceability matrix that traces through requirements, tests, incidents and tasks. Unfortunately, there are no ready-made SpiraTeam reports that does something like that so I had to write the template myself. As this was my first attempt to create xml/xslt template (I am embedded s/w guy), it is inefficient but does work. The template is based on Requirements Detailed template, so I suggest that if you were to use it, just clone the built-in template and replace the code with the one provided here. Heres how the output looks like: Req Name Relationship Related Req Task ID Test ID Incident ID Requirements PRJ-SRS-0001 Depends-on PRJ -PRS-001 TK5 TC101 IN201, IN202 PRJ -SRS-0002 Depends-on PRJ -PRS-002 TK6 TC102 IN204 PRJ -SRS-0003 Depends-on PRJ -PRS-003 TK7 TC103 IN205, IN207 Note that we are using custom requirements numbers in requirement name. The Software requirements are marked as SRS and project level requirements are marked as PRS. Heres the template. Req Name Relationship Related Req Task ID Test ID Incident ID 1>, 1>, 1>, TK 1>, TC 1>, IN en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/reports/1712.aspxthreadId=1712Vladimir Plotkin (Vladimir.Plotkin@creavomedtech.com) Recently, our QA/regulatory decided to run an audit and they requested a traceability matrix that traces through requirements, tests, incidents and tasks. Unfortunately, there are no ready-made SpiraTeam reports that does something like that so I had to write the template myself. As this was my first attempt to create xml/xslt template (I am embedded s/w guy), it is inefficient but does work. The template is based on Requirements Detailed template, so I suggest that if you were to use it, just clone the built-in template and replace the code with the one provided here. Heres how the output looks like: Req Name Relationship Related Req Task ID Test ID Incident ID Requirements PRJ-SRS-0001 Depends-on PRJ -PRS-001 TK5 TC101 IN201, IN202 PRJ -SRS-0002 Depends-on PRJ -PRS-002 TK6 TC102 IN204 PRJ -SRS-0003 Depends-on PRJ -PRS-003 TK7 TC103 IN205, IN207 Note that we are using custom requirements numbers in requirement name. The Software requirements are marked as SRS and project level requirements are marked as PRS. Heres the template. Req Name Relationship Related Req Task ID Test ID Incident ID 1>, 1>, 1>, TK 1>, TC 1>, IN Wed, 12 Jul 2017 08:56:57 -04002017-07-12T14:49:08-04:00/Support/Forum/spirateam/reports/1712.aspxmessageId=3060David J (adam.sandman+support@inflectra.com) Thanks Vladimir. Wed, 12 Jul 2017 14:49:08 -04002017-07-12T14:49:08-04:00/Support/Forum/spirateam/reports/1712.aspx#reply3060