<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: How to link a requirement to more then one release or iteration  (Thread)</title><description> Hello Forum     I am new in using SpiraTest. I wonder how I can link a requirement to more then one release or iteration.     Do you have the solution ?     Thanks and regards     HUgues     PS : I am using version     SpiraTest       v     5.4.0     .     4      |      en       </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/2152.aspx</link><item><guid isPermaLink="false">threadId=2152</guid><author>FAURE Hugues (hugues.faure-istria@soprasteria.com)</author><category domain="http://www.inflectra.com/kronodesk/thread/tag">requirements</category><category domain="http://www.inflectra.com/kronodesk/thread/tag"> multiple releases</category><title>How to link a requirement to more then one release or iteration </title><description> Hello Forum     I am new in using SpiraTest. I wonder how I can link a requirement to more then one release or iteration.     Do you have the solution ?     Thanks and regards     HUgues     PS : I am using version     SpiraTest       v     5.4.0     .     4      |      en       </description><pubDate>Wed, 04 Mar 2020 15:32:36 -0500</pubDate><a10:updated>2024-08-27T12:54:40-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/2152.aspx</link></item><item><guid isPermaLink="false">messageId=3740</guid><author>David J (adam.sandman+support@inflectra.com)</author><title> Hello  That is not possible. A requirement can only be linked to one release or sprint/iteration.  </title><description> Hello  That is not possible. A requirement can only be linked to one release or sprint/iteration.  Regards  David </description><pubDate>Wed, 04 Mar 2020 19:43:38 -0500</pubDate><a10:updated>2020-03-04T19:43:38-05:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/2152.aspx#reply3740</link></item><item><guid isPermaLink="false">messageId=3875</guid><author>Staci Smith (staci@servicecore.com)</author><title> Hello @inflectra.david ,  As a follow-up to hfaureis question.  In SpiraTest, what is the best prac</title><description> Hello @inflectra.david ,  As a follow-up to hfaureis question.  In SpiraTest, what is the best practice on a requirement that has changed/updated.  For example:  Requirement-01 was linked to Release-A.  Release-B, Release-C have happened and now, some months later Requirement-01 is modified or improved in some way, therefore slightly changing. Should I update the Requirement-01 to be linked to the next time it will be released in Release-D?  Something else?     Thanks, Staci </description><pubDate>Wed, 04 Nov 2020 23:12:30 -0500</pubDate><a10:updated>2020-11-04T23:12:30-05:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/2152.aspx#reply3875</link></item><item><guid isPermaLink="false">messageId=6628</guid><author>Tenley P (teresa.langston+support@inflectra.com)</author><title> It is now possible to link a requirement to more than one Release via the Associations tab on the R</title><description> It is now possible to link a requirement to more than one Release via the Associations tab on the Requirement detail page.  This enhancement was included in the  release of version 7.5 March 2023 .  You can read more about this functionality in SpiraDocs  here  and  here . </description><pubDate>Fri, 08 Mar 2024 22:04:52 -0500</pubDate><a10:updated>2024-03-08T22:04:52-05:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/2152.aspx#reply6628</link></item><item><guid isPermaLink="false">messageId=6629</guid><author>Ilia Poliakov (ilya.polyakov@edetek.com)</author><title> Yes, restrictions removal what is allowed to be associated with is very useful!  Waiting to be be a</title><description> Yes, restrictions removal what is allowed to be associated with is very useful!  Waiting to be be able to associate any entity with any project wide.  As some strange restrictions are still exists in Spira  (associations mechanism is developed and amazing but somehow not entities are allowed to be associated).  I want to be able to associate any entity with any and project wide.    This will allow me to create map of dependencies for example...  </description><pubDate>Mon, 11 Mar 2024 12:23:55 -0400</pubDate><a10:updated>2024-03-11T12:23:55-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/2152.aspx#reply6629</link></item><item><guid isPermaLink="false">messageId=6715</guid><author>Ilia Poliakov (ilya.polyakov@edetek.com)</author><title> Looking forward to see that Spira allows to associate any entity with any entity from any project. </title><description> Looking forward to see that Spira allows to associate any entity with any entity from any project. This will unblock great potential of Spira. </description><pubDate>Wed, 29 May 2024 08:21:09 -0400</pubDate><a10:updated>2024-05-29T08:21:09-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/2152.aspx#reply6715</link></item></channel></rss>