<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: Associating requirements from different projects (Thread)</title><description> Hi,    I would like to know if the following functionality is available or planned for Spira:    For requirements one can define "Associations". Unfortunately,  the "Add new Association" dialog only allows to choose from requirements in the current project.     For our development setup it would make sense to have the respective requirements in separate projects and allow to link between those requirements. (Example: A national standard provides a lengthy list of requirements that some - not all - projects needs to fulfill. Since I don't want to copy all requirements from this national standard into each project it would make sense to define them once in a separate project and only link to the individual project requirements.)    Thanks for your response!    Christoph </description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/spiratest/issues-questions/165.aspx</link><item><guid isPermaLink="false">threadId=165</guid><author>Christoph Fabianek (christoph.fabianek@frequentis.com)</author><title>Associating requirements from different projects</title><description> Hi,    I would like to know if the following functionality is available or planned for Spira:    For requirements one can define "Associations". Unfortunately,  the "Add new Association" dialog only allows to choose from requirements in the current project.     For our development setup it would make sense to have the respective requirements in separate projects and allow to link between those requirements. (Example: A national standard provides a lengthy list of requirements that some - not all - projects needs to fulfill. Since I don't want to copy all requirements from this national standard into each project it would make sense to define them once in a separate project and only link to the individual project requirements.)    Thanks for your response!    Christoph </description><pubDate>Wed, 28 Sep 2011 15:27:26 -0400</pubDate><a10:updated>2022-10-20T21:27:47-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/165.aspx</link></item><item><guid isPermaLink="false">messageId=329</guid><author>David J (adam.sandman+support@inflectra.com)</author><title>Currently SpiraTest is based on the model of independent, separate projects where data cannot be lin</title><description>Currently SpiraTest is based on the model of independent, separate projects where data cannot be linked between them. One workaround would be to use the URL Attachment option to link the items together.</description><pubDate>Tue, 04 Oct 2011 15:51:01 -0400</pubDate><a10:updated>2011-10-04T15:51:01-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/165.aspx#reply329</link></item><item><guid isPermaLink="false">messageId=5769</guid><author>David J (adam.sandman+support@inflectra.com)</author><title> This was extended in v5.1 a while back to allow cross-project associations:   https://www.inflectra</title><description> This was extended in v5.1 a while back to allow cross-project associations:   https://www.inflectra.com/Ideas/Entry/spira-51--cross-project-associations-403.aspx  </description><pubDate>Thu, 20 Oct 2022 21:27:47 -0400</pubDate><a10:updated>2022-10-20T21:27:47-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/165.aspx#reply5769</link></item></channel></rss>