witAdmin: Customize and manage objects for tracking work
Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013
With witadmin, you can modify XML definition files to support the On-premises XML process model. For an overview of process models and what is supported, see Customize your work tracking experience.
You can change how you track your team's progress by creating and customizing objects that track work items. By using the witadmin command-line tool, you can create, delete, import, and export objects such as categories, global lists, global workflow, types of links, and types of work items. You can also permanently delete types of work item types, and you can delete, list, or change the attributes of fields in work item.
The witadmin command-line tool is not supported on Azure DevOps Services. Instead, you use inherited processes.
As the following illustration shows, you manage categories and types of and work items for each project. You manage global lists, types of links, and fields in work item for each project collection. You can customize global workflow for a project or a collection.
With witadmin, you can import and export definition files. Other tools you can use include the Process Editor (requires that you have installed a version of Visual Studio). Install the TFS Process Template editor from the Visual Studio Marketplace. You can use this version of the Process Editor to modify the old-style work item forms. You can't use it to edit forms associated with the new web forms.
Or, you can use the TFS Team Project Manager, an open-source client available from GitHub.
For most commands, you must be a member of the Project Administrators or Project Collection Administrators groups. For more information, see Add an administrator.
How to run the witadmin command-line tool
To run the witadmin command-line tool, open a Command Prompt window where Visual Studio is installed. The witadmin command-line tool installs with any version of Visual Studio. You can access this tool by installing the free version of Visual Studio Community or Visual Studio Team Explorer.
If you are connecting to TFS, you must use the same version of Visual Studio or Team Explorer as TFS. For example, if you connect to a TFS 2017 instance, you must connect from Visual Studio 2017 or Team Explorer 2017. There is no Team Explorer 2015 version.
Visual Studio 2017 or Team Explorer 2017 client:
%programfiles(x86)%\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer
Enterprise in place of
Community, depending on the version you've installed.
Visual Studio 2015 client:
cd %programfiles(x86)%\Microsoft Visual Studio 14.0\Common7\IDE
Visual Studio 2013 client:
cd %programfiles(x86)%\Microsoft Visual Studio 12.0\Common7\IDE
Team Explorer 2013 client:
cd %programfiles%\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer
On a 32-bit edition of Windows, replace %programfiles(x86)% with %programfiles%. You can install Visual Studio Community (which provides access to Team Explorer) or Visual Studio Team Explorer 2017 for free.
You can use the following parameters to display help text for witadmin.
|Displays the syntax and parameters for the witadmin command-line tool.|
|Displays the syntax and parameters for the witadmin command that you specify.|
All work tracking objects—such as, work item types (WITs), process configuration, global lists— are customized by their XML definitions.
All witadmin commands can be run against an on-premises TFS. If you are new to work tracking customization and for definitions of the work tracking objects your can customize, see Customize your work tracking experience.
- destroywitd: Delete a WIT
- exportwitd: Export a WIT file
- importwitd: Import a WIT file
- listwitd: List WIT names
- renamewitd: Change a WIT display name
- deletefield: Delete a field
- listfields: List field attributes
- indexfield: Turn field indexing on/off
- changefield: Change a field attribute
- exportprocessconfig: Export the ProcessConfiguration file
- importprocessconfig: Import the ProcessConfiguration file
- deletelinktype: Delete a link type
- exportlinktype: Export a link type file
- importlinktype: Import a link type file
- listlinktypes: List the defined link types
- reactivatelinktype: Reactivate or rename a link type
- destroygloballist: Delete a global list
- exportgloballist: Export the global list
- importgloballist: Import the global list
- listgloballist: List all global list names
- exportglobalworkflow: Export the global workflow file
- importglobalworkflow: Import the global workflow file
- destroywi: Permanently delete work items
- rebuildcache: Rebuild the client cache
- exportcategories: Export the Categories file
- importcategories: Import the Categories file
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.