Team Services (Hosted XML) | TFS 2017 | TFS 2015 | TFS 2013
This topic applies to team project customization for Hosted XML and On-premises XML process models. For the Inheritance process model, see Customize a process.
For an overview of process models, see Customize your work tracking experience.
You customize the initial configuration of team projects by customizing one or more process template files. You can customize several types of template files, which include the root XML file, plug-in files, and XML definition files. By customizing these files, you can define the initial configuration of all team projects that are created from the process template.
Client support for team project creation
When you choose to create a team project, the Project Creation Wizard (PCW) reads the root process template file and its specified plug-in files defined within the process or process template you select. These files define the tasks and the screens that appear when the PCW is run. (No screens appear when you create a team project from the web portal.)
For example, if a process template includes the plug-in for Windows SharePoint Services, then a screen appears that requests information about the project portal.
Depending on whether you work from the cloud or an on-premises server, you can create a team project from one of the following clients.
|Client||Team Services||On-premises TFS|
(- Supported; - Not supported)
For Team Services, even if you initiate creating a team project from Visual Studio or Team Explorer, you'll be taken to the web portal to complete the operation.
When you create a team project from the web portal, there are several plug-ins that aren't supported. They are simply ignored by the PCW. For details, review Plug-in file descriptions and PCW support.
The root process template file
You customize the root XML file, ProcessTemplate.xml, to define the sequence of plug-in files to be processed and the dependencies of each plug-in. The ProcessTemplate.xml file contains all task groups that must run to successfully create a team project. Each task group references a subordinate XML plug-in file (often in a subfolder) where the specific tasks are defined. For more information, see Define the root tasks.
Each plug-in file configures a specific functional area by defining one or more tasks. Tasks specify to upload a file, set permissions for a group, or configure some other functional area.
For example, the Work Item Tracking plug-in configures the work item types, queries, categories, and process configuration for a new team project.
Plug-in file descriptions and PCW support
Each default process template includes the plug-in files described in the following table. The order in which the plug-ins are called is determined by the root process template file. Except for the Classification plug-in, plug-ins can also be deleted from the process template.
All plug-ins are supported () when you create your team project from a supported client. However, when you create the team project from the cloud or the web portal for an on-premises TFS, several plug-ins are ignored or not supported () as indicated in the following table.
|Plug-in folder and file||Client||Web portal||Description|
|Defines the initial security permissions used by Team Foundation Build and uploads build template files. (Need to check with NC about whether these files are of use with Team Services or latest non-XAML build defintions).|
|Configures the initial area and iteration or sprint paths. Also uploads the Microsoft Project Mapping (FileMapping.xml) file that defines how work tracking fields map to Office Project fields.|
|Groups and Permissions
|Defines the initial security groups, teams, team members, and their permissions.|
|Defines the initial security permissions that are assigned to identities for Visual Studio Lab Management.
|Creates the Report Manager site for the team project and uploads the Reporting Services reports. Only supported for on-premises TFS.
To add reports after creating a team project, see Add reports to a team project.
|Defines the initial test variables, configurations, settings, and resolution states of a team project. This plug-in also uploads the information contained in the following files:
|Defines the initial security permissions for Git or Team Foundation version control (TFVC),l and for TFVC, tcheck-in notes and whether exclusive check-out is required.|
Windows SharePoint Services
|Defines the project portal based on a template for a SharePoint site. Only supported for on-premises TFS. This plug-in also uploads the information contained in the following files and folders:
To add a project portal site after creating a team project, see Configure or add a project portal.
Work Item Tracking
|Defines the initial work item types, queries, and work item instances of a team project. Team members use work items to track work. A work item type defines the fields, workflow, and form used to track work. To customize any of these objects after you create a team project, see Customize your work tracking experience.
This plug-in also uploads the information contained in the following files and folders:
The schema definition for process templates uses a mix of camel-case and all capitalized elements. If you encounter errors when validating your type definition files, check the case structure of your elements. Also, the case structure of opening and closing tags must match according to the rules for XML syntax. See Process template plug-ins: Index to XML element definitions.