Can we migrate to a new TFS process template and keep history

tfstfs-process-templatetfs-workitem

We are currently using TFS 2008 with the Scrum for Team System template from Conchango, with a few minor tweaks. We are looking at upgrading to TFS 2010 and we are considering moving to the MSF for Agile template.

What is the best way to move to a new process template and keep history? I'd like to be able to create a new team project on the TFS 2010 server, get everything checked-in, and move our source to the new project. It would be nice if we could somehow keep the check-in comment history and possibly even be able to navigate back to the work item history associated with a changeset in the old project. I'd even be willing to migrate the old project as-is over to 2010 and then move the source to a new project, retaining the old project with work items only in 2010.

Has anyone gone through the process that can over some advice?

Best Answer

We have been through this painful process. Here is some useful information:

Yes we used latest release of TFS Integration platform.
This blog is your friend for TFS Integration platform.
Take a look at mapping xml files here
Refer this forum. It has lot of good information.
Also see "Upgrading your Process Template in Team Foundation Server" and "Process Template Upgrade #3 – Destroy all Work Items and Import new ones".

Related Solutions

How to change Process Template on an existing Team Project in TFS 2010

Once you've created a Team Project, you unfortunately can't just upload a new process template. As Robaticus says, you'll have to download the XML for the template and modify it, then re-upload it. The power tool lets you create NEW templates for NEW team projects, but it won't modify an existing one.

Instead, you can use the witadmin.exe tool (on any computer with Team Explorer installed, under \Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE, or just from a Visual Studio Command Prompt) to export the current workitem definitions and re-import them once you've made your changes.

Luckily, if you're not using workitem tracking much, then this might not be too difficult. You might be able to just delete all the existing workitem types and then re-upload the new types.

If this is too much trouble, consider how much you want to retain your source control history. It might be worth creating a new Team Project with the Agile template and then just moving all your source code into it.

Steps for changing process template for an existing project in TFS 2010

Given that you aren't using any existing work item types, your final proposal looks like the best option.

After deleting the old reports and exporting the SharePoint documents (you could also use Windows Explorer instead of stsadm), there are actually two commands in 'tfpt' that will help you. This will reduce it from 14 steps down to 5 or 6 steps.

tfpt addprojectreports  Add or overwrite reports for an existing team project
tfpt addprojectportal   Add or move portal for an existing team project

tfpt addprojectreports /collection:http://yourtfs:8080/tfs/YourCollection /teamproject:"Your Team Project" /processtemplate:"Microsoft Visual Studio Scrum 1.0" /verbose
tfpt addprojectreports /collection:http://yourtfs:8080/tfs/YourCollection /teamproject:"Your Team Project" /processtemplate:"Microsoft Visual Studio Scrum 1.0" /verbose

Best Answer

Related Solutions

How to change Process Template on an existing Team Project in TFS 2010

Steps for changing process template for an existing project in TFS 2010

Related Topic