Skip Navigation LinksHome Page > Forums > SpiraTeam Forums > SpiraTeam Best Practices > Recommendation for cross-...
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? I'm unclear of the difference (other than Portfolios require SpiraPlan).
Thanks in advance.
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 association's types.
The recommended approach is to use Product Associations:
That way you can share requirements across projects/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.