A customer wanted a RTM report that looped per row for each requirement, rather than having a set of requirements IDs concatenated with commas: his section displays a list of all the requirements with the associated test cases/requirements. Req # Name Type Status Release # Test Traceability Requirements Traceability RQ4 Ability to add new books to the system Feature Developed 1.0.0.0.0001 TC2,TC13,TC8 RQ6 RQ4 Ability to add new books to the system Feature Developed 1.0.0.0.0001 TC2,TC13,TC8 RQ30 RQ5 Ability to edit existing books in the system Feature Tested 1.0.0.0.0001 TC3,TC8 RQ57 RQ5 Ability to edit existing books in the system Feature Tested 1.0.0.0.0001 TC3,TC8 RQ7 RQ5 Ability to edit existing books in the system Feature Tested 1.0.0.0.0001 TC3,TC8 RQ31 RQ6 Ability to delete existing books in the system Feature Tested 1.0.0.0.0002 TC8,TC12 RQ4 RQ7 Ability to associate books with different subjects Feature Developed 1.1.0.0.0001 TC4,TC8 RQ5 RQ57 Ability to report on book editions Feature Accepted TC4,TC2,TC5 RQ5 RQ30 Creating a new book in the system Use Case Completed TC2 RQ4 RQ31 Editing an existing book in the system Use Case Completed TC3 RQ5 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/1777.aspxthreadId=1777David J (adam.sandman+support@inflectra.com)custom report xslt rtm traceability matrix A customer wanted a RTM report that looped per row for each requirement, rather than having a set of requirements IDs concatenated with commas: his section displays a list of all the requirements with the associated test cases/requirements. Req # Name Type Status Release # Test Traceability Requirements Traceability RQ4 Ability to add new books to the system Feature Developed 1.0.0.0.0001 TC2,TC13,TC8 RQ6 RQ4 Ability to add new books to the system Feature Developed 1.0.0.0.0001 TC2,TC13,TC8 RQ30 RQ5 Ability to edit existing books in the system Feature Tested 1.0.0.0.0001 TC3,TC8 RQ57 RQ5 Ability to edit existing books in the system Feature Tested 1.0.0.0.0001 TC3,TC8 RQ7 RQ5 Ability to edit existing books in the system Feature Tested 1.0.0.0.0001 TC3,TC8 RQ31 RQ6 Ability to delete existing books in the system Feature Tested 1.0.0.0.0002 TC8,TC12 RQ4 RQ7 Ability to associate books with different subjects Feature Developed 1.1.0.0.0001 TC4,TC8 RQ5 RQ57 Ability to report on book editions Feature Accepted TC4,TC2,TC5 RQ5 RQ30 Creating a new book in the system Use Case Completed TC2 RQ4 RQ31 Editing an existing book in the system Use Case Completed TC3 RQ5 Tue, 28 Nov 2017 18:45:07 -05002018-08-13T06:17:53-04:00/Support/Forum/spirateam/reports/1777.aspxmessageId=3166David J (adam.sandman+support@inflectra.com) Heres the XSLT you should use for this report: Req # Name Type Status Release # Test Traceability Requirements Traceability RQ padding-left: px; 1">, TC RQ Tue, 28 Nov 2017 18:45:36 -05002017-11-28T18:45:36-05:00/Support/Forum/spirateam/reports/1777.aspx#reply3166messageId=3368Tung Nguyen (tran.nguyen@transport.nsw.gov.au) Hello Adam, Wed like to have a trace between requirements to test cases to test results (latest), can you please advise to achieve that? What wed like to see in the table REQ1 - Req Name - TC1 - Test Results (i.e. Pass/Fail) If theres a req covered by 2 TCs, we want to see that requirement splitted into 2 rows for each TC Thanks, Mon, 13 Aug 2018 06:17:53 -04002018-08-13T06:17:53-04:00/Support/Forum/spirateam/reports/1777.aspx#reply3368