Forums > SpiraTest Forums > SpiraTest Best Practices > requirements and multiple...
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.
We also have the same need - to share requirements across multiple projects. Has there been any additions for this?
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.
results match your keyword(s)