We recommend using Visual Studio 2017

witimport

[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]

Important note Important

The witimport command is obsolete. Use the witadmin command instead. For more information, see witAdmin: Administrating Work Item Tracking Objects.

Use the witimport command to validate and import a work item type from an XML file to a team project on a Team Foundation Server. If you try to import a work item type that already exists in the specified team project, a warning prompt asks if you want to overwrite the existing work item type.

You can validate a work item type without importing it by using the /v option.

The witimport command-line utility is located in Drive:\Program Files\Visual Studio 10.0\Common7\IDE on the Team Explorer client computer.

Required Permissions

To use the witimport command, you must be a member of the Team Foundation Administrators security group or the Project Administrators security group. For more information, see Team Foundation Server Permissions and Team Foundation Server Default Groups, Permissions, and Roles.

Note Note

Even if you are logged on with administrative credentials, you must open an elevated Command Prompt to perform this function on a server that is running Windows Server 2008. To open an elevated Command Prompt, click Start, right-click Command Prompt, and click Run as Administrator. For more information, see the Microsoft Web site.


witimport /f filepath /t tfs /p teamproject [/v] [/e encodingname]

Parameter

Description

/f filepath

The path to the XML definition file that contains the work item type to be imported.

Note Note
If the client computer runs Windows Vista, you may not have permissions to certain folders. If you try to export the global list to a location where you do not have permissions, the registry virtualization technology automatically redirects the exported file and saves it to the virtual store. For more information, see the Microsoft Web site: Registry Virtualization and Common file and registry virtualization issues in Windows Vista. To avoid this redirection, you can export the file to a location where you have permissions.

/t tfs

The computer name of the Team Foundation Server to which the work item type will be imported, or a fully specified URL for a Team Foundation Server.

/p teamproject

The team project to which the work item type will be imported. This team project must exist on the Team Foundation Server specified by tfs.

/e Encodingname

The name of a .NET Framework 2.0 encoding. The specified encoding will be used to import the work item type XML. If this argument is not specified, witimport uses UTF-8 encoding by default.

/?

Displays the witimport context help.

Option

Description

/v

Validate the XML file without importing.

The command in this example reads the file myworkitem.xml, validates the work item type it contains, and imports the validated work item to the AdventureWorks team project on the Team Foundation AdventureWorksServer. This example imports the work item type using the default UTF-8 encoding.

>witimport /f myworkitem.xml /t AdventureWorksServer /p AdventureWorks

The following example shows a command that uses a URL instead of a Team Foundation Server name. This example imports the work item type using the default UTF-8 encoding.

>witimport /f myworkitem.xml /t http://TFS:8080/bis/registration.asmx /p AdventureWorks

The following example validates and imports the work item using Unicode (utf-7) encoding.

>witimport /f myworkitem.xml /t AdventureWorksServer /p AdventureWorks /e utf-7

The following example validates the work item type in the file myworkitem.xml without importing it. This example validates the work item type using the default UTF-8 encoding.

>witimport /f myworkitem.xml /t AdventureWorksServer /p AdventureWorks /v

Show: