23

I'm using Visual Studio Team Services (previously Team Foundation Service, not Team Foundation Server) and I need to migrate a team project process template from Agile to Scrum.

Doe anyone know how to do it?

Esther Fan - MSFT
  • 8,276
  • 4
  • 27
  • 25
Carlos Coelho
  • 566
  • 1
  • 5
  • 14

1 Answers1

18

There are a couple of different ways to go about this, depending on what you want at the end. Most importantly, there is no way to change the process template from one to the other inside a Team Project, so you'll have to create a new Team Project with the Scrum Template to migrate to.

If you want history & attachments: Then you need to use the TFS Integration Platform. You'll create a xml mapping to flow the work items and source code from one project to the other. There are quite a few issues with going this direction including, history is compressed, the tool is notoriously finicky, shared steps (and other things) don't migrate and more. This is definitely not the recommended option, but sometimes you don't have a choice. Here's where to get the tool: http://visualstudiogallery.msdn.microsoft.com/eb77e739-c98c-4e36-9ead-fa115b27fefe

If don't need history, or can keep the other Team Project around: For this method, moving the code is easy (it's even easier if you've got a Git project, and you'll get history. Use the git-tf functionality to move your source to Git). Just check out from one repository, switch your workspace mapping and check in to the new repository.

To move your work items, use work item queries and export them to Excel. Then copy/paste into a second Excel spreadsheet and upload them to the new Project. This is by far the easiest method. Here's a detailed explanation:

1) From Agile template project: for each work item type that you want to move, create a work item query to pull all the ones you want and export them all to Excel (for example a query to pull all requirements and another for tasks)

2) From the Scrum template project: create a work item query for each work item type that you want to import and export it to Excel. It's going to be blank, but you're going to use this Excel spreadsheet to upload in a minute.

3) Copy/past from one Excel spreadsheet to the other, being careful to NOT copy column headers. A neat trick is to copy the History column from the old project into the Comments field in the new project.

4) Publish the results. Viola, you're migrated.

Andrew Clear
  • 7,910
  • 5
  • 27
  • 35
  • Hi Andrew, some of this solutions work only for Team Foundation **Server**, and using the online version Team Foundation **Service**. Anyway, u gave some good ideas, and I'll try some of them. – Carlos Coelho Nov 18 '13 at 21:03
  • 1
    Which ones? Both of those options should work for VSOnline I believe. – Andrew Clear Nov 18 '13 at 21:38
  • 1
    That's right! Migration using the Integration platform should work. "export"/"import" using Excel, Git or cross project branch will be easiest. – jessehouwing Nov 21 '13 at 16:46
  • 2
    Tried both approaches - TFS integration platform and Excel copy-paste. Both are painful. TFS integration platform didn't work properly, was shutting down sometimes and consuming a lot of memory. It was pretty unstable in my case and the UI was hanging all the time, so it was almost impossible to work with. The installation is also a pain. When doing it in Excel sheet, I was required to do a lot of replaces. E.g., you can't set bug status to Resolved (at least I was unable) as internal workflow requires a new bug to be in status New. Also, it was time-consuming with my 2000+ workitems. – TechGeorgii Jul 25 '14 at 10:14
  • 5
    "Viola, you're migrated." - images of a stringed instrument crossing the Atlantic – ExStackChanger Feb 17 '16 at 12:33