Hi, part of our organization works with multiple products (each having their own releases), sharing some requirements. How do I manage requirement coverage for this? As requirements can only be linked to 1 release, I cannot link them to each product(release) the apply to. eg: requirement A is applicable for - product 1 release 2.0 - product 2 release 1.5 how to organize releases to cope with this? Will spira 4.1 introduce products in requirements? and if so, how do they relate to releases? thx for your reply! Filip 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/best-practices/710.aspxthreadId=710Filip Baert (filip.baert@newtec.eu) Hi, part of our organization works with multiple products (each having their own releases), sharing some requirements. How do I manage requirement coverage for this? As requirements can only be linked to 1 release, I cannot link them to each product(release) the apply to. eg: requirement A is applicable for - product 1 release 2.0 - product 2 release 1.5 how to organize releases to cope with this? Will spira 4.1 introduce products in requirements? and if so, how do they relate to releases? thx for your reply! Filip Thu, 12 Sep 2013 13:42:59 -04002016-06-28T22:43:07-04:00/Support/Forum/spiratest/best-practices/710.aspxmessageId=1292David J (adam.sandman+support@inflectra.com) Hi Filip Version 4.1 is adding Components to projects, so those could be used as ways of decomposing a system down into smaller sub-products. I'm not sure if this will address the multiple release issue though. Currently each requirement is only capable of being associated to one release. Regards Adam Fri, 13 Sep 2013 17:35:57 -04002013-09-13T17:35:57-04:00/Support/Forum/spiratest/best-practices/710.aspx#reply1292messageId=1294Filip Baert (filip.baert@newtec.eu) indeed, that does not solve my problem. My wish would be that you have a following logical relation: requirement product + release (n on n relationship) so if you only have 1 product, situation would be as it is now in version 4.0 if you have multiple products, one can assign a requirement to each individual product if needed. Test cases would not be touched as you already link them now to multiple releases. any thoughts? Mon, 16 Sep 2013 07:17:03 -04002013-09-16T07:17:03-04:00/Support/Forum/spiratest/best-practices/710.aspx#reply1294messageId=1877Jen Leger (jen.leger@bmm.com) Hi, We also have the same need - to share requirements across multiple projects. Has there been any additions for this? Thanks, Jen Thu, 09 Oct 2014 11:16:46 -04002014-10-09T11:16:46-04:00/Support/Forum/spiratest/best-practices/710.aspx#reply1877messageId=1895Jon Freed (jfreed@edmap.com)FYI, we have resolved this through the following structure: 1. We only have one SpiraTeam project. It is our "Enterprise" project. So, that allows us to keep requirements in one place across multiple products and releases. (Incidentally, the Spira roadmap says that a future release will allow items to be referenced in multiple projects.) 2. We don't use the component field. Instead, we have a hierarchy of requirements and one branch in the hierarchy is products/systems. (So, within that branch we have requirement line items that represent products and things within those products, like screens.) 3. Instead of tying business requirements to components, we instead tie requirements in the business requirement branch to requirements in the product branch. Wed, 22 Oct 2014 13:29:36 -04002014-10-22T13:29:36-04:00/Support/Forum/spiratest/best-practices/710.aspx#reply1895messageId=2487rd-sw-hernis eaton (rd-sw-hernis@eaton.com) Hi, We have similar issues on sharing same requirement on multiple projects. For example we have HW and SW side projects for each product line. The same requirement has to be shared in both HW and SW projects. The report has to be from the business requirement to both SW and HW project tests. Right now it is very hard as we duplicate requirement in both the projects and reports also are 2. Jon, I dont quite understand your solution for this issue. Could you please explain with an example on how did you workaround? Anyone can throw light on this would be highly appreciated. Thank your for the reply in advance. Cheers, Durga. Thu, 18 Feb 2016 08:33:11 -05002016-02-18T08:33:11-05:00/Support/Forum/spiratest/best-practices/710.aspx#reply2487messageId=2673Erwin Husmann (erwin.husmann@casema.nl) I agree with Jon. one SpiraTeam project should be sufficient for sharing requirements among different products. You might try to create products as test cases (or vice versa). Requirements can be shared among test cases Try to use releases to test cases, not in requirements. regards Erwin Tue, 28 Jun 2016 22:43:07 -04002016-06-28T22:43:07-04:00/Support/Forum/spiratest/best-practices/710.aspx#reply2673