How to link a requirement to more then one release or iteration

Hello

That is not possible. A requirement can only be linked to one release or sprint/iteration.

Regards

David

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

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.

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...

Looking forward to see that Spira allows to associate any entity with any entity from any project. This will unblock great potential of Spira.