I tried many ways, but it doesn't seems to work... 1. I created a new project, and checked the "Based on Existing Project". Results: it doesn't import none of the requirements (nor the tasks) 2. I exported the requirements from project A to project B. Results: I only exported the requirements, BUT didn't export their corresponding tasks. 3. I made a copy of a Project A. Result: The new copy has only the requirement of the original... NO Tasks copied. 4. I also exported the tasks from Project A to project B. Results: The task did migrate, but they weren't linked to their corresponding requirements--even when I did export the requirements before hand. 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/303.aspxthreadId=303Noureddine Bouslah (nbouslah@hotmail.com) I tried many ways, but it doesn't seems to work... 1. I created a new project, and checked the "Based on Existing Project". Results: it doesn't import none of the requirements (nor the tasks) 2. I exported the requirements from project A to project B. Results: I only exported the requirements, BUT didn't export their corresponding tasks. 3. I made a copy of a Project A. Result: The new copy has only the requirement of the original... NO Tasks copied. 4. I also exported the tasks from Project A to project B. Results: The task did migrate, but they weren't linked to their corresponding requirements--even when I did export the requirements before hand. Mon, 09 Jul 2012 10:39:24 -04002012-08-17T11:50:33-04:00/Support/Forum/spirateam/issues-questions/303.aspxmessageId=585David J (adam.sandman+support@inflectra.com) You are correct, none of these methods will copy the tasks associated with the requirements. We are about to release a project backup/restore/migration tool that will allow you to migrate complete projects (including requirements and tasks) that will be able to do this. It should be released next week. Mon, 09 Jul 2012 14:18:40 -04002012-07-09T14:18:40-04:00/Support/Forum/spirateam/issues-questions/303.aspx#reply585messageId=587Noureddine Bouslah (nbouslah@hotmail.com)Thanks Adam. This will be a handy workaround. The issue with duplicating a requirement with its task still remains correct? For instance, this wouldn't help if I want to duplicate [withing the same project] for example a couple of requirements with their associated tasks, or would it? Mon, 09 Jul 2012 17:11:21 -04002012-07-09T17:11:21-04:00/Support/Forum/spirateam/issues-questions/303.aspx#reply587messageId=627David J (adam.sandman+support@inflectra.com) No, I'm afraid not.Fri, 27 Jul 2012 19:18:24 -04002012-07-27T19:18:24-04:00/Support/Forum/spirateam/issues-questions/303.aspx#reply627messageId=670Andreas Bernhard (andreas.bernhard@leaseplan.ch) Hi Adam, I have a similar issue. For a year now we have stored requirements as separate projects. We would like to change that now. We would like to have a project called something like "Maintenance". Under that project we would store the requirements. Is it possible to migrate the projects with their test cases to requirements? Thank you very much for your reply Fri, 17 Aug 2012 11:50:33 -04002012-08-17T11:50:33-04:00/Support/Forum/spirateam/issues-questions/303.aspx#reply670