TFS 2013 - Transfer project command code and history to a new project using a different process template

I just completed a successful upgrade from TFS2010 to TFS2013 in a UAT environment. An example of this was using the SCRUM pattern. However, all migrated projects use the Agile template, which was the default at the time they were created in 2010. My research on this led me to the idea that they could not be changed locally. Instead, it seems to me that I need to create a new project and then transfer the code history? I am stuck here on how to do this.

Can this be confirmed? Ideally, all I want to do is change the template, I only care about the history of code registration in current projects.

Another option I found is to use TFS integration tools. But I do not think this supports TFS2013. These are installation errors requesting Team Explorer 2010,2008.

Can anyone help where I'm wrong?

thanks

+6
source share
4 answers

Thanks to timB33 for pointing me in the right direction.

To solve this problem, I modified the script found here .

set pt=C:\Microsoft Visual Studio Scrum 2013\ set tpc=http://servername:8080/tfs/DefaultCollection set tp=MyAgileTP REM #1 Do Renames witadmin renamewitd /collection:%tpc% /p:%tp% /n:"User Story" /new:"Product Backlog Item" /noprompt witadmin renamewitd /collection:%tpc% /p:%tp% /n:"Issue" /new:"Impediment" /noprompt REM #2 Apply new Template witadmin importwitd /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\TypeDefinitions\Bug.xml" witadmin importwitd /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\TypeDefinitions\CodeReviewRequest.xml" witadmin importwitd /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\TypeDefinitions\CodeReviewResponse.xml" witadmin importwitd /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\TypeDefinitions\FeedbackRequest.xml" witadmin importwitd /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\TypeDefinitions\FeedbackResponse.xml" witadmin importwitd /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\TypeDefinitions\Impediment.xml" witadmin importwitd /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\TypeDefinitions\ProductBacklogItem.xml" witadmin importwitd /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\TypeDefinitions\SharedStep.xml" witadmin importwitd /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\TypeDefinitions\Task.xml" witadmin importwitd /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\TypeDefinitions\TestCase.xml" witadmin importwitd /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\TypeDefinitions\Feature.xml" REM #3 Import Link Types just in case coming from 2008 witadmin importlinktype /collection:%tpc% /f:"%pt%WorkItem Tracking\LinkTypes\SharedStep.xml" witadmin importlinktype /collection:%tpc% /f:"%pt%WorkItem Tracking\LinkTypes\TestedBy.xml" REM #4 Import Categories witadmin importcategories /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\categories.xml" REM #5 Import ProcessConfig witadmin importprocessconfig /collection:%tpc% /p:%tp% /f:"%pt%WorkItem Tracking\Process\ProcessConfiguration.xml" 

I ran this (pointing it to the loaded template, seeing the first pt variable), and then I was able to use all the functionality of the SCRUM process. I have not fully tested this yet, but it seems to be a winner. Since my other option was to transfer the version control to another Team project, but there was a limitation here, I lost my entire history of managing the version label. I just didn’t feel like going. Hope this helps others.

Thanks,

+4
source

You can update in-situ templates through the (witadmin script or) tfs powertools plugin, this will allow you to export the SCRUM work item template and then import it into an existing project, overwriting it with WIT.

+1
source

It appears that the new project has installed the migrated template by default.

To change the default value: In the command explorer, click on Settings → Process Template Manager and change the default template for this project in the window that opens. Hope this helps.

0
source

The TFS integration platform works with TFS 2013. Errors during installation with the Team Explorer query 2010,2008 can be resolved by installing Visual Studio 2012. The error is related to the missing TFS library model.

0
source

Source: https://habr.com/ru/post/958996/


All Articles