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. Hosted XML customization supports adding and updating global lists with a process update. To learn more, see Differences between Team Services and TFS process template customizations.
The Inheritance process model doesn't support global lists. For an overview of process models, see Customize your work tracking experience.
By using global lists, you can minimize the work that is required to update a list that appears in the definitions of several work item types (WITs). Global lists are pick lists that you can include within one or more fields and WIT definitions.
You can share list items among several WITs for a collection by including the list items in one or more
As you define WITs, you might find that some fields share the same values. Frequently, you can share across several WITs and even across several team projects. Some of these values, such as the build number of nightly builds, change frequently, which requires an administrator to frequently update these lists in many locations. Global lists can be especially useful when a list must be derived from an external system. For example, suppose a company maintains a separate customer database. When you file a bug that a customer discovered, the customer's name is entered into a custom
Found By Customer field.
You can manage global lists for a collection as an XML file that you can list, import, export, and delete. The name of each global list can have up to 254 Unicode characters and must be unique within a collection.
There are no system-defined nor predefined global lists specified in the default processes or process templates provides.
For the team project collection where the global lists are defined, you must have the following permissions set:
To export or list global lists, you must be a member of the Project Collection Valid Users group or have your View collection-level information permission set to Allow.
To import global lists, you must be a member of the Project Collection Administrators security group.
To add or modify a global list, use the witadmin command-line tool to import and export the definition for global lists. See Manage global lists. To use a global list, add it to the
FIELD definition within a work item type. See All FIELD elements.
Add and manage global lists
A global list is a set of
LISTITEM elements that is stored and used globally by all team projects in a collection. Global lists are useful for fields that are defined within several types of work items, such as Operating System, Found in Build, and Fixed in Build.
You can define one or more global lists and their items by using one of the following methods in the following ways based on the process model you use:
- Within a WIT XML definition that you add to a team project or process template (Hosted XML and On-premises XML)
- Within a global list XML definition file that you import to a team project collection (On-premises XML)
- Within a global workflow XML definition file that you import to a team project collection (On-premises XML).
For the Hosted XML process model, the following limits are placed on global list import:
- Total of 64 global lists
- Total of 512 items per list
- Approximately 10K items can be defined total within all global lists specified across all WITs.
The following table describes the GLOBALLIST and LISTITEM elements. You can use these elements to enumerate a list of values that is presented to the user as a pick list or drop-down menu of items.
Defines a set of LISTITEM elements that are stored for a collection and that all team projects in a collection can use.
globalListName: A string of text that contains between 1 and 255 characters.
GLOBALLIST is a required child element of the GLOBALLISTS element and an optional child element of the
Defines a valid list value. Global lists must not include project-scoped groups because they are not scoped to a project.
LISTITEM is a required child element of GLOBALLIST and an optional child element of the
Sample global list
By adding the following syntax, you can define a global list within an XML definition file for a type of work item or a global workflow:
<GLOBALLISTS> <GLOBALLIST name="name of global list"> <LISTITEM value="List item 1" /> <LISTITEM value="List item 2" /> <LISTITEM value="List item 3" /> <LISTITEM value="List item 4" /> . . . <LISTITEM value="List item n" /> </GLOBALLIST> </GLOBALLISTS>
By using the following syntax, you can reference a global list within an XML definition file for a type of work item:
<GLOBALLISTS> <GLOBALLIST name=" name of global list 1" /> <GLOBALLIST name=" name of global list 2" /> . . . <GLOBALLIST name=" name of global list n" /> </GLOBALLISTS>
Sample global list maintained for a project collection
To add a global list to a project collection, you can import the following syntax by using the witadmin importgloballist command:
<gl:GLOBALLISTS xmlns:gl="http://schemas.microsoft.com/VisualStudio/2008/workitemtracking/globallists"> <GLOBALLIST name="NameOfGlobalList"> <LISTITEM value="ListItem1" /> <LISTITEM value="ListItem2" /> <LISTITEM value="ListItem3" /> <LISTITEM value="ListItem4" /> . . . <LISTITEM value="ListItemN" /> </GLOBALLIST> </gl:GLOBALLISTS>
A global list cannot be empty. Each
GLOBALLIST element must have at least one
LISTITEM element defined.
Are any global lists auto-populated with data?
Yes for on-premises TFS. The global list named Builds–TeamProjectName gets appended each time a build is run. Over time, the list can become very long. Best practice is to routinely remove unused items from the list.
To learn more about using this list, see Fields that support integration with test, build, and version control.