Mappings between Requirements & Tasks lost when copying between projects

Wednesday, December 5, 2018


I have a challenge relating to mappings between artefacts being lost when moving across projects. My use case is described below:

I need to store a base set of requirements, tasks, test cases and test sets within a library project. Each time we bring a new customer on board we need to create a new project and copy the relevant requirements, tasks, test sets and test cases to enable us to test our service capability for that customer.

I’ve created a bunch of requirements with assigned tasks and test cases which are assigned to test sets within a dummy project to test this out. When I try to copy selected requirements from the library to a new project, I lose the mapping to tasks. I would then have to copy the tasks and manually re-link them to the relevant requirements.

Based on my very small sample size of 7 requirements, with an average of 17 tasks per requirement this is going to be unworkable when I scale up to (potentially) a couple of hundred requirements per customer.

I note from dated 2012 that this exact issue was being encountered back then. The comments mention the release of a project backup/restore/migration tool, but unfortunately this tool appears to require being run by the administrator and does not seem to cater to my use case. It simply backs up/restores an entire project or allows you to transfer a project between server instances.

I need to be able to select specific requirements and their associated tasks from the library project rather than blanket copying all requirements and tasks. I’d also like to be able to do the same with test cases and test sets.

At the moment this is looking like a show-stopper for wider adoption of SpiraTeam within my organisation.

Does anyone have any advice as to how I can achieve the above without having to resort to manually re-mapping tasks to requirements and test cases to test sets, each time I want to on board a new customer?

1 Replies
Wednesday, December 5, 2018
re: moebiusone Wednesday, December 5, 2018


We recommend simply copying the "base" project as your new project, that will copy over the appropriate data with all the mappings intact. This is done on the Administration > View Projects page. Just click Copy / Clone (the label varies between versions) and that's it.

You can then delete anything you don't need from the destination project.



Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885


  • Started: Wednesday, December 5, 2018
  • Last Reply: Wednesday, December 5, 2018
  • Replies: 1
  • Views: 4689