Recently we upgraded from TFS 2013.2 (german) to TFS 2015.1 (english). Now if I create a new project collection and a new team project I can only select the old german process templates
"Microsoft Visual Studio Scrum 2013.2"
"MSF for Agile Software Development 2013.2"
"MSF for CMMI Process Improvement 2013.2"
The description below the templates is in german, consequently I believe I have only the old process templates installed on our TFS.
I found the correct templates here:
C:\Program Files\Microsoft Team Foundation Server 14.0\Tools\Deploy\ProcessTemplateManagerFiles\1033
How can I re-install the original current process templates from TFS 2015.1 in english?
Where are the active templates stored? In the database? Can I "inject" the correct ones somehow?
Deleting and re-importing the templates is not possible because TFS locks the default templates now. Unfortunately the wrong default templates...
You can upload these project templates in Visual Studio under Team -> Team Project Collection Settings -> Process Template Manager and there is an upload button.
The problem that you are going to face is that any projects currently using one of the older templates will not be transferable to the new ones.
You should be able to remove the old ones from this window also provided that there are no projects using them.
Related
We are migrating a TFS 2012 project to TFS 2013 (project only has work items and no source code) and have a few questions about the agile project template.
In TFS 2012 if we want to create an Agile project then we have to choose: MSF for Agile Software Development 6.2
In TFS 2013 if we want to create an Agile project then we have to choose: MSF for Agile Software Development 2013.3
I want to know the following:
Why is it that the TFS 2012 project with above template has a folder under it called 'BuildProcessTemplates', whereas the TFS 2013 project has no such folder?
What is significance of the 'BuildProcessTemplates' folder, does the workitems data get stored in it? Can we get rid of it without affecting the workitem data?
We are migrating a TFS 2012 project into TFS 2013 so we are wondering if we can delete the 'BuildProcessTemplates' folder after migrating to TFS 2013 without affecting the WorkItems.
It's confusing terminology.
"Process Templates" and "Build Process Templates" are totally different things with no overlap.
A Process Template controls what work items you have available, how they interact, and the reports you get.
A Build Process Template controls how the TFS build system works. They are orthogonal to work items. You could delete the BuildProcessTemplates folder and it would have no impact on your work items, but I don't recommend doing so -- the folder contain the workflows that TFS can use to build your software for continuous integration or continuous delivery.
As of TFS2013, the folder isn't created because the built-in templates are stored internally. You only need to create a folder for the build process templates if you want to use custom templates, or modify the existing templates.
I am currently looking to migrate an existing TFS2008 server to a new VS2012 server.
A major part of the reason behind this is that we want to be able to use the Microsoft Visual Studio Scrum template, however I am struggling to determine whether VS2008 is able to manipulate work items created using this template (according to all of the blogs and/or other information I can find, the templates can only be installed to a VS2010 or VS2012 server, but there is nothing clear about Visual Studio clients). I believe that both VS2010 and VS2012 can access an manipulate items based upon these templates.
Note: We HAVE to use VS2008 at the moment as some of the projects are for mobile devices (Windows/CE, Windows Mobile) and, as I am sure you will be aware, these projects are not supported by VS2010 or VS2012).
I am aware of the compatibility GDR's for both VS2008 and VS2010, but again they mention nothing specific about the scrum templates.
So, my question is simple...
Can I access and manipulate (add new work items, update existing items, create a sprint etc) a TFS project that is based upon one of the Microsoft Visual Studio Scrum templates on Team Foundation Server 2012 from Team Explorer 2008/Visual Studio 2008.
Work Item process templates (e.g. VS Scrum) have nothing to do with the version of the client used to connect to TFS, which means that any version of Visual Studio (2008, 2010, or 2012) will work with TFS 2012, regardless of the process template (Scrum, Agile MSF or CMMI).
Furthermore, the forward compatibility GDR provides the team explorer extension (window) that will give VS 2008 the ability to use the new functionality of TFS 2012 (e.g. start and end dates for iterations, capacity planning, etc.).
The process template (i.e. Visual Studio Scrum 2.0) is nothing but a set of XML documents detailing which work item types you will have, what fields they contain, some reports, SharePoint settings, security settings, etc. None of these affect or are affected by the version of Visual Studio.
I have created a new team project using sfts v3.0 project template. Later I have realized that we need to customize scrum template (add some new status). How can I upgrade the scrum template once team project has been created. Can I modify the template and overwrite files to location where it is on TFS 2010 server?
The new project I have created is entirely blank and I am running migration tool to migrate source code from tfs 2008 to tfs 2010 and I don't want to interrupt that process.
Use the Process Editor of the TFS Power Tools.
Here's a guide how to use it.
I installed Microsoft Scrum 1.0 template from their website, it installed with no errors but it is not being shown in the Templates list when I try to create a New Team Project. There is only MSF Agile and MSF CMMI.
What could be causing this?
When you choose upload, you need to browse c:\Program Files\Microsoft\Microsoft Visual Studio Scrum 1.0\Process Template, which is the folder that contains the ProcessTemplate.xml root file.
You have to upload the process template to your server:
In the Visual Studio 2010 choose from the menu TEam -> Team Project Collection Settings -> Process Template Manager. In the dialog choose Upload
Here is a blog post that details the steps to upload and install the template.
http://blogs.msdn.com/b/cdndevs/archive/2010/07/19/microsoft-visual-studio-scrum-1-0.aspx
I have an TFS server installation that through time has gone through upgrades from TFS 2005 to TFS 2008 and then to TFS 2010.
During the lifetime of the installation a lot of projects have been created and different project templates have been used. MSF Agile 4.0, 4.1, 4.2 and 5.0. and a few MSF CMMI ones.
What I would like to do is "replace" the project template used for all these projects to use a new one common one: Microsoft Visual Studio Scrum 1.0.
I am aware that TFS project templates are used as templates for creating new projects and cannot modify the tfs projects definitions after creation.
Uptil now only the version control and build server part of TFS have been used and there are no existing work item types.
Additionally all projects and build scripts are depending on the source code paths stay the same.
As I see it I have the following options:
Create new TFS projects using the correct project template and then move/branch the source code to the new project.
All code is moved to a temporary team project.
The old project is deleted
New project with the original name and correct process template is created
Code is moved to the new team project
Temporary team project is deleted
All the build definitions needs to be to recreated which is not an option.
The source code move/branch will "mess up" the versioning history
By messing up the versioning history I mean that when you move source code it will behind the scenes do a delete + source rename on the original location and the history will still be located in the old project. This will make searching in the history difficult and if I actually delete the old project I will loose all the history before the source code move.
This is really not an option for me since there is years of code change history that is needed to for supporting the different applications being built.
Use the TFS migration tools to migrate to another TFS project
This has the same downsides as the first solution
Replace/import work item types, install new reports, create new SharePoint sites
For each tfs project
Delete existing work item definitions using "witadmin deletewitd"
Import each work item definition from the new process template using "witadmin importwitd"
Import work item categories using "witadmin importcategories"
Delete old reports in project folder in report server
Upload the report definitions from the new process template
Modify data sources used for the reports using the report manager to point to the correct shared data sources (TfsReportDS and TfsOlapReportsDS)
Modify the report parameter ExplicitProject default value to "" (empty string) and disable prompt user option.
Export the documents in the old SharePoint site using stsadm
Delete the old SharePoint site
Recreate the sharepoint site using the TFS2010 Agile Dashboard site template
Activate site feature "Team Foundation Server Scrum dashboard"
In TFS Project Settings -> Project Portal Settings: Enable "team project portal" and ensure the url is correct. Enable "reports and dashboards refer to data for this team project"
And finally..
Process the Warehouse
Process the Analysis Database
Even though that this involves a lot of small steps this looks more appealing because
this option will not force me to move the source code and my existing build definitions will be intact.
My question:
Are there other ways to achieve the replacement of work item types that I haven't mentioned?
And/or am I missing any steps in last solution?
Given that you aren't using any existing work item types, your final proposal looks like the best option.
After deleting the old reports and exporting the SharePoint documents (you could also use Windows Explorer instead of stsadm), there are actually two commands in 'tfpt' that will help you. This will reduce it from 14 steps down to 5 or 6 steps.
tfpt addprojectreports Add or overwrite reports for an existing team project
tfpt addprojectportal Add or move portal for an existing team project
tfpt addprojectreports /collection:http://yourtfs:8080/tfs/YourCollection /teamproject:"Your Team Project" /processtemplate:"Microsoft Visual Studio Scrum 1.0" /verbose
tfpt addprojectreports /collection:http://yourtfs:8080/tfs/YourCollection /teamproject:"Your Team Project" /processtemplate:"Microsoft Visual Studio Scrum 1.0" /verbose
Your first option is IMHO your best shot.
You can branch the sources from the old team project to the new team project. With TFS 2010 you can see the history also from the branched location. So you don't loose functionality in here.
The Build is just an msbuild file which is stored in source control. The only thing you have to do is actually copy the build definitions. You can do that either manually, or you can create a little app that does that for you.