We have implemented a workflow utilizing SpiraTeam as follows: We maintain a substantial repository of test cases, numbering in the hundreds. Each time we receive a new build version, we have historically duplicated the entire test case folder and appended new test cases to this duplicated folder. This approach allows us to conduct a comparative analysis of changes by contrasting the contents, while also enabling us to perform test case executions on both the previous server build by referencing the original folder and on the new server build using the updated test case folder. Are there alternative methods to streamline this process, allowing us to differentiate between test cases associated with version 1 and version 2, without the necessity of duplicating test cases into new folders? Thank you! 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/issues-questions/2839.aspxthreadId=2839Sasa Zdravkovic (szdravkovic@smithmicro.com) We have implemented a workflow utilizing SpiraTeam as follows: We maintain a substantial repository of test cases, numbering in the hundreds. Each time we receive a new build version, we have historically duplicated the entire test case folder and appended new test cases to this duplicated folder. This approach allows us to conduct a comparative analysis of changes by contrasting the contents, while also enabling us to perform test case executions on both the previous server build by referencing the original folder and on the new server build using the updated test case folder. Are there alternative methods to streamline this process, allowing us to differentiate between test cases associated with version 1 and version 2, without the necessity of duplicating test cases into new folders? Thank you! Wed, 16 Aug 2023 20:03:09 -04002024-01-02T19:38:49-05:00/Support/Forum/spirateam/issues-questions/2839.aspxmessageId=6174David J (adam.sandman+support@inflectra.com) You can simply map the same test cases to the new release. Then (and only when) test cases need to change, you can clone them to keep the originals and the new versions. That is another option. Fri, 18 Aug 2023 00:24:29 -04002023-08-18T00:24:29-04:00/Support/Forum/spirateam/issues-questions/2839.aspx#reply6174messageId=6180Sasa Zdravkovic (szdravkovic@smithmicro.com) Thank you! Wed, 23 Aug 2023 19:32:54 -04002023-08-23T19:32:54-04:00/Support/Forum/spirateam/issues-questions/2839.aspx#reply6180messageId=6563Ilia Poliakov (ilya.polyakov@edetek.com) And when Spira adds the ability to map builds to requirements, incidents (not only if you have git integration) you may have much more power: you will be able to select build during testrun execution and you will know (and track) precise build that you are testing and easily see what features were included there. Mon, 01 Jan 2024 08:20:04 -05002024-01-01T08:20:04-05:00/Support/Forum/spirateam/issues-questions/2839.aspx#reply6563