Inflectra Customer Forums: Exporting test case templates to another project results in duplicates (Thread) For our projects, we use some test case templates, that contain variables like ${Condition} and ${Action}. Then, it is possible to link these from other test cases where there variables are replaced with some parameters. When we export test cases (the linked ones and the templates) to another project (for reuse), we run into some issue: Suppose we have a collection of test cases that used the same template(s), and these test cases are spread over multiple folders. When we export this collection to another project, the same folder structure is created in the new project. However, for each test case that links to a template, a new copy of that template is made in the same folder as it is linked in. This results in a lot of additional templates that are all similar. But this is not 'our' purpose of a template. Is there a way to prevent this behavior? en-US(C) Copyright 2006-2024 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/1017.aspxthreadId=1017Stefan van Loenhout (svloenhout@huisman-nl.com)Exporting test case templates to another project results in duplicates For our projects, we use some test case templates, that contain variables like ${Condition} and ${Action}. Then, it is possible to link these from other test cases where there variables are replaced with some parameters. When we export test cases (the linked ones and the templates) to another project (for reuse), we run into some issue: Suppose we have a collection of test cases that used the same template(s), and these test cases are spread over multiple folders. When we export this collection to another project, the same folder structure is created in the new project. However, for each test case that links to a template, a new copy of that template is made in the same folder as it is linked in. This results in a lot of additional templates that are all similar. But this is not 'our' purpose of a template. Is there a way to prevent this behavior? Wed, 01 Oct 2014 14:28:26 -04002014-10-03T14:38:02-04:00/Support/Forum/spirateam/issues-questions/1017.aspxmessageId=1857Stefan van Loenhout (svloenhout@huisman-nl.com) Stefan van Loenhout For our projects, we use some test case templates, that contain vari Stefan van Loenhout For our projects, we use some test case templates, that contain variables like ${Condition} and ${Action}. Then, it is possible to link these from other test cases where there variables are replaced with some parameters. When we export test cases (the linked ones and the templates) to another project (for reuse), we run into some issue: Suppose we have a collection of test cases that used the same template(s), and these test cases are spread over multiple folders. When we export this collection to another project, the same folder structure is created in the new project. However, for each test case that links to a template, a new copy of that template is made in the same folder as it is linked in. This results in a lot of additional templates that are all similar. But this is not 'our' purpose of a template. Is there a way to prevent this behavior? Thu, 02 Oct 2014 07:36:52 -04002014-10-02T07:36:52-04:00/Support/Forum/spirateam/issues-questions/1017.aspx#reply1857messageId=1858Stefan van Loenhout (svloenhout@huisman-nl.com) Whoops, something went wrong. I wanted to comment that it is even worse, the copied 'templates Whoops, something went wrong. I wanted to comment that it is even worse, the copied 'templates' have lost their parameters as well.Thu, 02 Oct 2014 07:42:24 -04002014-10-02T07:42:24-04:00/Support/Forum/spirateam/issues-questions/1017.aspx#reply1858messageId=1864Kat A (support2@inflectra.com) Hi Stefan, This is a known issue when exporting test cases that have links. I'm sorry for t Hi Stefan, This is a known issue when exporting test cases that have links. I'm sorry for the inconvenience. Next year, we are planning to release SpiraTeam version 4.3, in which the test case organization functionality will be completely redesigned. So the issue will be solved at that time. For now, the only workaround I can think of is this: Those linked test cases (templates) won't get duplicated if you export a folder that contains all of the test cases that use them. I know you said that they are currently spread over multiple folders. But if you copy them all into a single folder, and then export that folder, you should end up with only one copy of each template. Regards, Elise Fri, 03 Oct 2014 14:38:02 -04002014-10-03T14:38:02-04:00/Support/Forum/spirateam/issues-questions/1017.aspx#reply1864