Forums > SpiraTest Forums > SpiraTest Best Practices > Multiple Projects Vs. Sin...
We have an array of related products that share many of the same requirements and test cases. Since SpiraTest treats projects as independent entities, we cannot easily share requirements and test cases between them. Should we consider using a single project?
Generally we recommend using a single large project if the various products are highly related and share the same requirements and test cases. This can be done by simply making each project it's own separate Release Tree. So in the Release Hierarchy you'd have:
On the other hand, if your products are largely independent of each other, we would recommend using separate projects to keep things simple.
Creating a common release is a theorte
results match your keyword(s)