Inflectra Customer Forums: Deprecating old requirements (Thread) If RQ123, implemented as part of Release 1.0, is being removed as part of Release 2.0, what is the preferred way of handling this in SpiraTeam? I see that requirements can be marked "Obsolete". But how do you track that the requirement removal work is being performed as a requirement for Release 2.0? Is it best to create a separate requirement for this new work? Something rubs me the wrong way about having a requirement that specifies that some bit of functionality should be removed from the system. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/best-practices/234.aspxthreadId=234Greg Ferreri (gferreri@glneurotech.com)Deprecating old requirements If RQ123, implemented as part of Release 1.0, is being removed as part of Release 2.0, what is the preferred way of handling this in SpiraTeam? I see that requirements can be marked "Obsolete". But how do you track that the requirement removal work is being performed as a requirement for Release 2.0? Is it best to create a separate requirement for this new work? Something rubs me the wrong way about having a requirement that specifies that some bit of functionality should be removed from the system. Tue, 24 Jan 2012 15:27:20 -05002012-10-01T11:33:30-04:00/Support/Forum/spirateam/best-practices/234.aspxmessageId=463David J (adam.sandman+support@inflectra.com)That's probably the best way to do it for now. We're considering adding a "removed in release" fieldThat's probably the best way to do it for now. We're considering adding a "removed in release" field to requirements to better capture this.Fri, 27 Jan 2012 21:39:55 -05002012-01-27T21:39:55-05:00/Support/Forum/spirateam/best-practices/234.aspx#reply463messageId=724Andy Smith (andy.smith@infoterra-global.com)Hi Adam I agree with Greg that creating an RQ that simply relates to the removal of another RQ is aHi Adam I agree with Greg that creating an RQ that simply relates to the removal of another RQ is a bit strange. Adding a "removed in release" field to requirements would be great. Have you considered this any further in your roadmapping? Cheers Andy Mon, 01 Oct 2012 11:33:30 -04002012-10-01T11:33:30-04:00/Support/Forum/spirateam/best-practices/234.aspx#reply724