如何更改 TFS 2010 中现有团队项目的流程模板？
如何将 TFS 2010 中现有团队项目的流程模板更改为 MSF for Agile？
我们已将 TFS 2008 升级到 2010，现在我还想将流程模板更改为 MSF for Agile（当前为 CMMI）。 我们没有太多使用工作项功能，因此如果转换中丢失一些信息也没关系。
How do I change process template to MSF for Agile on an already existing team project in TFS 2010?
We have upgraded our TFS 2008 to 2010, and now I would also like to change the process template to MSF for Agile (currently CMMI).
We haven't used the workitem functionality much so if some information gets lost in the conversion doesn't matter.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
不幸的是，创建团队项目后，您不能只上传新的流程模板。正如 Robaticus 所说，您必须下载模板的 XML 并对其进行修改，然后重新上传。该强大工具可让您为新团队项目创建新模板，但不会修改现有模板。
相反，您可以使用 witadmin.exe 工具（在任何安装了 Team Explorer 的计算机上，位于 \Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE 下，或者仅通过 Visual Studio 命令提示）导出当前工作项定义并在进行更改后重新导入它们。
幸运的是，如果您不经常使用工作项跟踪，那么这可能不会太困难。您也许可以删除所有现有的工作项类型，然后重新上传新类型。
如果这太麻烦，请考虑您希望保留多少源代码管理历史记录。可能值得使用敏捷模板创建一个新的团队项目，然后将所有源代码移入其中。
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.
您无法更改流程模板，但可以更改工作项类型。因此，对于错误、任务，您可以换成敏捷定义。
您可以在 2010 年使用
witadmin来完成此操作，2008 年则使用importwit，首先将模板下载到磁盘（为此，您需要 TFS 强大工具）。然后将控制台应用程序指向 bug.xml、task.xml 等。Usage: witadmin importwitd /collection:collectionurl [/p:project] /f:filename [/e:encoding] [/v] /collection Specifies the Team Foundation project collection. Use a fully specified URL such as http://servername:8080/tfs/Collection0. /p Specifies the team project in which the new work item type is imported. This is required, except when the validation-only option is used. /f Specifies the work item type XML definition file to import. /e Specifies the name of the .NET Framework 2.0 encoding used to import the XML file. For example, /e:utf-7 will use Unicode (UTF-7) encoding. Encoding is automatically detected whenever possible. If the encoding cannot be detected, UTF-8 is used. /v Validates the XML definitions for the work item type, link type, or global workflow without importing them.You can't change the process template, however you can change the work item types. So for bugs, tasks you can swap to the Agile definitions.
You can do this in 2010 with
witadmin, in 2008 it'simportwit, by first downloading the template to disk (you'll need the TFS power tools for this). Then point the console app at bug.xml, task.xml etc..Usage: witadmin importwitd /collection:collectionurl [/p:project] /f:filename [/e:encoding] [/v] /collection Specifies the Team Foundation project collection. Use a fully specified URL such as http://servername:8080/tfs/Collection0. /p Specifies the team project in which the new work item type is imported. This is required, except when the validation-only option is used. /f Specifies the work item type XML definition file to import. /e Specifies the name of the .NET Framework 2.0 encoding used to import the XML file. For example, /e:utf-7 will use Unicode (UTF-7) encoding. Encoding is automatically detected whenever possible. If the encoding cannot be detected, UTF-8 is used. /v Validates the XML definitions for the work item type, link type, or global workflow without importing them.您可以将敏捷流程模板导出到磁盘，然后将工作项导入到现有项目中。您可能需要 TFS Power Tools 来执行此操作。
You can export the agile process template to disk, then import the work items into your existing project. You may need the TFS Power Tools to do this.
我可能来不及回答这个问题了，但是 TFS 集成平台 工具在这里确实可以提供帮助。
请参阅此问题< /a> 服务器故障，详细介绍了如何从 Scrum For Team System V2 迁移到 Microsoft Visual Studio Scrum 1.0。
您需要设置自己的映射才能从模板移动到目标模板，但过程是相同的。
I may be too late for this question, but the TFS Integration Platform tools could really help here.
See this question on server fault that details on how to move from Scrum For Team System V2 to Microsoft Visual Studio Scrum 1.0.
You would need to setup your own mappings to move from your templates to the target template, but the process is the same.
请注意，witadmin.exe 在某些情况下可能会有所帮助，但 TFS 集成平台是您完成此任务的最终选择。有一个 用户声音 项目仍在等待处理。请检查这个SO线程。
Please note witadmin.exe could help in some scenarios but TFS Integration Platform is your ultimate choice to achieve this task. There is a user voice item still pending. Please check this SO thread.
我认为实现此目标的最佳方法是使用“新”流程模板创建一个新的团队项目，并使用 TFS 集成工具迁移现有的工作项并选择从源代码管理创建一个新分支，这样您将有新的工作项目（具有新的工作流程）和源代码控制历史记录（以及）。您甚至可以跨版本的 TFS 执行此操作！ （对迁移 TFS 2005/2008/2010 感兴趣的情况）
另一种方法可能是使用工作项模板，但我认为这更多的是应用于工作项的一种视觉样式（我没有太多经验）。为此，只需右键单击您的项目，导入 WITDefinition 并通过选择在所需的 WorkITem 上应用模板来应用模板。
I think the best way to accomplish this is to create a new Team Project with "the new" process template and use the TFS Integration tool to migrate your existing WorkItems and choose create a new branch from Source Control, so you'll have new work Items (with the new workflow) and the source control history (as well). You'd even do this across versions of TFS!! (On the case interested on migrate TFS 2005/2008/2010)
Another way might be to use the WorkItem Templates, but I think this is more a kind-of visual style (I've not much experience) applied to the Work Item. To do so, just right click on your project, import the WITDefinition and apply the template by selecting Apply template on desired WorkITems.