Porting TFS 2010 to Visual Studio Online

I have installed the OpsHub VSO Migration Utility and I am trying to migrate one of our smallest projects as a test.

By creating a new benchmarking project in VSO, the error validation is not correct.

The existing TFS 2010 project is based on the MSF template for Agile Software Development v5.0, and the new VSO project is MSF for Agile Software Development 2013.3.

As far as I know, none of these templates have been customized.

For each work item type, the mismatched fields are:

  • RelatedLinkCount
  • AreaID
  • AttachedFileCount
  • HyperLinkCount
  • ExternalLinkCount
  • IterationID

Installed version of the utility v1.1.0.005

Any help would be greatly appreciated.

+3


source to share


3 answers


Between TFS 2005/2008 and TFS 2010, the process templates were updated to add extra space to the display name for each of the fields you specify. In this case, you can take a few simple steps to work around and then rerun the OpsHub Visual Studio Migration Utility.

You will need a tool witadmin.exe

and in particular changefield

. Here are the steps you want to take to change the display names of each of the fields to include spaces:



witadmin.exe changefield /collection:http://tfs.contoso.local:8080/tfs/DefaultCollection /n:System.RelatedLinkCount /name:"Related Link Count"
witadmin.exe changefield /collection:http://tfs.contoso.local:8080/tfs/DefaultCollection /n:System.AreaId /name:"Area ID"
witadmin.exe changefield /collection:http://tfs.contoso.local:8080/tfs/DefaultCollection /n:System.AttachedFileCount /name:"Attached File Count"
witadmin.exe changefield /collection:http://tfs.contoso.local:8080/tfs/DefaultCollection /n:System.HyperLinkCount /name:"Hyperlink Count"
witadmin.exe changefield /collection:http://tfs.contoso.local:8080/tfs/DefaultCollection /n:System.ExternalLinkCount /name:"External Link Count"
witadmin.exe changefield /collection:http://tfs.contoso.local:8080/tfs/DefaultCollection /n:System.IterationId /name:"Iteration ID"

      

Give them a try and I hope it works as a workaround for you!

+5


source


OpsHub unfortunately has to fix this, or you can use a different tool.

When you try to migrate, the OpsHub tool compares your process template between the two projects and pops its toys out of the stroller if they don't match. In your case, your 2010 server was once in either 2005 or 2008. In TFS versions prior to 2010, conflicting fields did not have spaces, since 2010 they are ... Due to a mismatch.

There are other, less nanny state, migration methods, but they are much more complicated.



  • TFS Integration Tools - This tool is free, supported by Microsoft, but extremely complex. It was built for enterprise consultants to move TFS data. Not fun, but can be made to work.
  • Excel Transfer - You can simply use excel to move the tip of the work items and move the tip of the TFVC source. Or go to Git in VSO and use Git-TFS to move with history for source.
  • Hire someone (invite / ALM consultant). Most ALM MVPs are consultants and have the tools to move your stuff.

I would assume that # 1 and # 3 have the same value at the end of the day, and # 2 tends to be unpopular.

Check out the ALM Rangers Migration Guide .

+1


source


Because this is exactly our scenario (TFS2008> TFS2010> VSO) and we also got an error when migrating work items from OVSMU from TFS2010 to VSO. I was willing to give the workaround as described by Ed. To make it more convenient, I tried it not from the command line, but with Visual Studio 2012 from the Tools: Process Editor: Work Item Types: Open WIT from Server menu. The first attempt was to set the work item type. After changing all the relevant names, I was asked if I wanted to save the changes to the item. After clicking Yes, I got a message box:

"Microsoft Visual Studio: Work Item Type: Task TF26177: The System.IterationId field could not be renamed from Iterative ID to Iteration ID. There were validation errors. Continuing to save may cause the file to become inactive, you want to continue ? "

Do you have some additional tips for me to get this all to where I can move the work items?

0


source







All Articles