We have requirements and testcase at several levels. Some testcases are only for the particular level (top, sub, subsub GǪ.) and others are for the several levels . In Spira we can only link testcases to the lowest level. 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/spiratest/issues-questions/119.aspxthreadId=119Bert vermeulen (bert.vermeulen@intraffic.nl) We have requirements and testcase at several levels. Some testcases are only for the particular level (top, sub, subsub GǪ.) and others are for the several levels . In Spira we can only link testcases to the lowest level. Thu, 21 Jul 2011 06:46:09 -04002012-10-17T17:43:19-04:00/Support/Forum/spiratest/issues-questions/119.aspxmessageId=231David J (adam.sandman+support@inflectra.com)We plan on removing this limitation in our next (v3.2) release.Tue, 26 Jul 2011 16:16:33 -04002011-07-26T16:16:33-04:00/Support/Forum/spiratest/issues-questions/119.aspx#reply231messageId=722Andy Smith (andy.smith@infoterra-global.com) Hi We have SpiraTeam v3.2 and we cannot do this. When you select any mid -level requirement in the coverage browser, only the lowest -level RQ appears to be mapped. Has this change only been applied to SpiraTest not SpiraTeam? Please advise. Andy Mon, 01 Oct 2012 10:09:53 -04002012-10-01T10:09:53-04:00/Support/Forum/spiratest/issues-questions/119.aspx#reply722messageId=766David J (adam.sandman+support@inflectra.com) It didn't make it into v3.2, it will be in v4.0.Wed, 17 Oct 2012 17:43:19 -04002012-10-17T17:43:19-04:00/Support/Forum/spiratest/issues-questions/119.aspx#reply766