Hi there, We have a broad set of products and use SpiraTeams to track requirements, test cases, releases and so on. We often have to create regression test suites that span products, for example to verify support for new OS versions or if we have a large multi-product release. We are in the planning phase for a large requirements restructure but what is the recommendation on how we should store requirements so that we can create test suites that span products? We will need to be able to easily manage cross-product testing and report on test runs and incidents. Will Programs work here? Or Portfolios? Im unclear of the difference (other than Portfolios require SpiraPlan). Thanks in advance. Don 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/best-practices/2597.aspxthreadId=2597Don McKelvie (dmckelvie@stayinfront.com) Hi there, We have a broad set of products and use SpiraTeams to track requirements, test cases, releases and so on. We often have to create regression test suites that span products, for example to verify support for new OS versions or if we have a large multi-product release. We are in the planning phase for a large requirements restructure but what is the recommendation on how we should store requirements so that we can create test suites that span products? We will need to be able to easily manage cross-product testing and report on test runs and incidents. Will Programs work here? Or Portfolios? Im unclear of the difference (other than Portfolios require SpiraPlan). Thanks in advance. Don Mon, 04 Apr 2022 21:39:53 -04002026-05-04T11:59:05-04:00/Support/Forum/spirateam/best-practices/2597.aspxmessageId=5632Ilia Poliakov (ilya.polyakov@edetek.com) Hi, Don! I support you with your question. We have similar problems. See please my topic Include a tesCase from one project into a testSet in another - Inflect (inflectra.com) Another proposal to Inflectra was to allow eny associations between any Spira entiities and allow to add custom associations types. Tue, 05 Apr 2022 07:28:31 -04002022-04-05T07:28:31-04:00/Support/Forum/spirateam/best-practices/2597.aspx#reply5632messageId=5633David J (adam.sandman+support@inflectra.com) The recommended approach is to use Product Associations: https://spiradoc.inflectra.com/Spira-Administration-Guide/Product-General-Settings/#product-associations That way you can share requirements across projects/products: https://spiradoc.inflectra.com/Spira-User-Manual/Requirements-Management/#viewing-requirements-from-shared-products You can then create a separate integration project that contains the test cases that map to the requirements from the other specific projects that have shared their requirements with this integration project/product. Tue, 05 Apr 2022 18:16:17 -04002022-04-05T18:16:17-04:00/Support/Forum/spirateam/best-practices/2597.aspx#reply5633messageId=6866David J (adam.sandman+support@inflectra.com) Hello, Good news, we have released new functionality that lets you have test cases in multiple products live in the same test set in a different product. The documentation on cross-product test sets is in SpiraDocs. Regards David Mon, 22 Jul 2024 19:52:14 -04002024-07-22T19:52:14-04:00/Support/Forum/spirateam/best-practices/2597.aspx#reply6866messageId=7382Victoria D (nino.diasamidze@inflectra.com) Dear Don, Export a Test Set to another product functionality is now available starting from Spira v.8.12This will copy the Test Set along with its Test Cases and Test Steps. For more information please refer to the documentation here: https://spiradoc.inflectra.com/Spira-User-Manual/Test-Set-Management/#exporting-a-test-set-to-a-different-product Please log a support ticket if you need more assistance. Regards, Victoria - Wed, 17 Sep 2025 12:45:59 -04002025-09-17T12:45:59-04:00/Support/Forum/spirateam/best-practices/2597.aspx#reply7382messageId=7591peter peter (peter56marget@outlook.com) When planning a large requirements restructure that involves cross-product regression testing, the key is to organize requirements in a way that enables traceability, reuse, and flexible grouping across multiple products. Instead of siloing requirements strictly by product, consider structuring them into shared and product-specific components, using a hierarchical or modular approach. This allows common requirements (such as OS compatibility or shared features) to be linked across products, making it easier to build unified test suites. Thu, 02 Apr 2026 10:30:45 -04002026-04-02T14:51:57-04:00/Support/Forum/spirateam/best-practices/2597.aspx#reply7591messageId=7636Justin Paul (anwermughal42@gmail.com) Hi Don, Yes-this is exactly the kind of scenario where Programs vs Portfolios matters, and the distinction is important. Programs (SpiraTeam/SpiraTest level) are best when you want to group multiple products together for shared testing and reporting (like regression suites across products or OS compatibility testing). They allow you to keep separate products but still run unified test sets and track results across them. Portfolios (SpiraPlan) go a step further and are more about strategic management across multiple programs/projects , including higher-level reporting, planning, and governance. For your use case-cross-product regression testing and shared test suites- Programs are usually the right fit , because they let you: Organize shared requirements or test cases across products Build regression test sets that span multiple products Report on executions and incidents in a unified way A good structure is often: Keep requirements primarily at product level Create shared or linked test cases for cross-product scenarios Use Programs to assemble and execute regression suites across those products Its a bit like удалить лишние объекты с фото youre not changing each product separately, but carefully removing boundaries where needed so you can focus only on the relevant shared elements for regression testing and reporting. Mon, 04 May 2026 11:50:39 -04002026-05-04T11:50:39-04:00/Support/Forum/spirateam/best-practices/2597.aspx#reply7636