What is the best way to manage old test cases and to avoid that they are used in new test sets? You can set the status to obsolete but that doesnt block them to be still used. Is there a way to block future usage? Thanks 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/spiraplan/best-practices/2796.aspxthreadId=2796kim vijle (kvij@idirect.net)test case obsolete What is the best way to manage old test cases and to avoid that they are used in new test sets? You can set the status to obsolete but that doesnt block them to be still used. Is there a way to block future usage? Thanks Wed, 24 May 2023 09:08:16 -04002024-11-12T19:03:43-05:00/Support/Forum/spiraplan/best-practices/2796.aspxmessageId=6128David J (adam.sandman+support@inflectra.com) Hi Kim, Id recommend: Using the test case workflow status to mark test cases as Obsolete Inside the test case workflow editor, make the field Execution Status disabled for the status Obsolete Now the test cases cannot be executed while in that status (either directly or inside a test set). Wed, 24 May 2023 16:10:57 -04002023-05-24T16:10:57-04:00/Support/Forum/spiraplan/best-practices/2796.aspx#reply6128messageId=6227Tasmania DoH (spiraplanadmin@health.tas.gov.au) Hi This solves a problem for me in restricting old test cases. From the test case detail screen the execute function is greyed out. However, from the test case list screen the execute function is still there, and when I select it, it generates the crytic message: You need to pass in at least one test case. Tue, 14 Nov 2023 00:31:59 -05002023-11-14T00:31:59-05:00/Support/Forum/spiraplan/best-practices/2796.aspx#reply6227