Release Management Issue
We are in the process of rolling out TD and have run into an interesting issue regarding Domain and Project set-up. We are a large company that has multiple large and small projects for multiple applications going on at the same time; each one being installed on their own timeline. Because this process does not work real well, we are heading toward release management (early 2Q03), where we will bundle projects together and install them. We currently have TD structured by each individual project by test phase (SIT & UAT); in the future we need to have the projects roll-up into a release by test phase (the split between test phase is due to organization size and boundries).
The problem that I have found is that projects from their own TD project will start SIT without knowing what release they will be assigned to (don't know if this will be an issue with UAT) and will then need to be moved to the TD release project. The problem is that you cannot copy Test Sets in their entirety - any execution results will not copy to the other project, only the test plans.
Re: Release Management Issue
Haven't truly looked at this problem fully but I do know that I once created a copy without going thru the TD front end by simply using Explorer - copying an entire project in Access - renaming it and then activating it with a new name. Give it a shot..can't hurt.