如何将工作项从 TFS 迁移到 Visual Studio Team Services [英] How to migrate work items from TFS to Visual Studio Team Services

问题描述

我的团队目前使用本地 TFS 2012 服务器.我正在将所有内容迁移到 Visual Studio Team Services，以前称为 Visual Studio Online.我从一个测试项目开始，能够轻松地迁移所有代码，但不知道如何对工作项执行相同的操作.

My team currently works with an on-premises TFS 2012 server. I am migrating everything to Visual Studio Team Services, formerly Visual Studio Online. I am starting with a test project and was able to easily get all the code migrated, but can't figure out how to do the same for the work items.

有什么好的指南吗?

推荐答案

截至 2018 年 3 月 29 日的新选项:

New options as of March 29th 2018:

• TFS 到 VSTS 的迁移 - 官方导入选项，将 1 个项目集合导入 1 个 VSTS 帐户.它会自动导入备份中存储的所有内容.在撰写本文时，TFS 必须升级到 TFS 2018，并且必须删除一些工作项模板自定义(VSTS 上有一些记录良好的功能不可用).
• VSTS 同步迁移器 - Martining Hinshelwood，TFS 和 VSTS 迁移的无冕之王, 已经构建了自己的小工具，可以将工作项从一个服务器/帐户迁移到另一个.它甚至可以从一个团队项目迁移到另一个团队项目，同时在流程模板之间进行切换.
• VSTS Work Item Migrator - 微软还开源了一个项目它们在内部用于迁移工作项.它的功能不那么强大，但它是由 Microsoft 制造的.

• TFS to VSTS migration - The official import option which will import 1 project collection into 1 VSTS account. It automatically imports everything stored in the backup. At the point of writing this, the TFS must be upgraded to TFS 2018 and some work item template customizations must be removed (there are a few well documented features unavailable on VSTS).
• VSTS Sync Migrator - Marting Hinshelwood, the uncrowned king of TFS and VSTS migrations, has built his own little tool that can migrate work items from one server/account to another. It can even do migrations from one Team Project to another and while doing it switch between process templates.
• VSTS Work Item Migrator - Microsoft has also open sourced a project that they used internally to migrate work items. It's less powerful, but it was made by Microsoft.

上一个答案:

目前还没有一个真正好的故事.您的选择是:

At the moment there isn't a really good story. Your options are:

• 重新开始 - 最简单:)
• 重新开始并手动重新创建有价值的项目 - 这很痛苦，但过去一些团队已经做过这些事情.使旧 TFS 服务器保持只读模式，每次在旧系统中使用工作项时，您都需要在新系统中手动创建它，设置所有字段并上传附件.根据项目的数量，您需要花几个冲刺来迁移最重要的内容.
• 再等一会儿 - Microsoft 目前正在开发一个完整的保真导入选项，该选项将允许您上传项目集合，并且它将作为新的 VSTS 帐户公开(不可能将项目集合导入到现有帐户).
• 使用 Excel 进行导入/导出 - 适用于大多数工作项，您会丢失除父/子之外的附件和工作项链接.诀窍是从一个项目集合中提取，然后将所有字段(ID 除外)复制到绑定到目标项目集合的 Excel 工作表中.您将需要修复所有标识字段(当用户在本地具有与 VSTS 中完全相同的显示名称时效果最佳)，并且您必须使用状态 new 导入一次，然后在刚刚导入的值上通过当前状态/原因和再次同步.测试用例、计划、套件和共享步骤将不会在导入时保持完整的关系.该方法与此方法非常相似.
• 使用 TFS 集成工具 - 适用于大多数工作项类型，尽管它会丢失自定义看板状态和标签.不会导入测试用例、共享步骤及其关系.此选项将允许您导入导入工作项和源代码及其关系.
• 使用第 3 方解决方案 - 在当前可用的选项之外 OpsHub 提供最完整的解决方案.对于测试用例和源代码控制链接迁移，您正在查看价格昂贵的商业版.它仍然有一个一长串已知问题，我上次尝试过它，我遇到了许多需要他们支持才能解决的问题.

• Start over - easiest :).
• Start over and manually recreate items of value - It's a pain, but it's some teams have done these things in the past. keep the old TFS server available in read-only mode and each time you use a work item in the old system, you manually create it in the new one, set all the fields and upload the attachments. Depending on the number of items it'll take you a few sprints to migrate the most important stuff over.
• Wait a while longer - Microsoft is currently working on a full fidelity import option which will allow you to upload a Project Collection and it will be exposed as a new VSTS Account (it's not going to be possible to import a project collection into an existing account).
• Use Excel for import/export - Will work for most work items, you loose attachments and work item links other than parent/child. The trick is to extract from one Project Collection then copy all fields, except the ID to an Excel sheet bound to the target project collection. You will need to fix all Identity fields (works best when users have the exact same display name on premise as in VSTS) and you'll have to import once with state new and then past the current state/reason over the just imported values and sync again. Test Cases, Plans, Suites and Shared Steps will not be imported with their relations in tact. The approach would be very similar to this one.
• Use the TFS Integration Tools - Will work for most work item types, though it will loose custom kanban states and tags. Test cases, Shared steps and their relations will not be imported. This option will allow you to import import work items and source code with their relationships in tact.
• Use a 3rd party solution - Out of the available options currently OpsHub offers the most complete solution. For test case and source control link migration you're looking at the commercial edition, which comes at a steep price. It still has a long list of known issues and last time I tried it, I ran into numerous issues which required their support to resolve them.

如果您当前的工作项目状态对您来说很宝贵，那么有专门的 TFS 顾问会以这些类型的迁移为生，然后你可以联系他们.

There are specialized TFS consultants who live off these kinds of migrations if your current state of the work items is precious to you, then you could reach out to them.

另见:

• https://www.visualstudio.com/en-us/articles/adopting-vsts

这篇关于如何将工作项从 TFS 迁移到 Visual Studio Team Services的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！