How to Manually Import an Operational Issue WITD to TFS in System Center 2012 SP1


Updated: May 13, 2016

Applies To: System Center 2012 SP1 - Operations Manager

The information in this topic applies only to System Center 2012 SP1.

In System Center 2012 Service Pack 1 (SP1), Operations Manager integration with Team Foundation Server (TFS) introduces a new work item type, Operational Issue, which must be present in each team project that synchronization uses. Generally, the TFS Work Item Synchronization Configuration Wizard can import this work item type definition (WITD). In some cases, however, you must manually import the WITD directly to TFS. You must manually import the Operational Issue WITD in the following cases:

  • A separate TFS administrator controls the development process model in TFS.

  • You are running the TFS 2010 Object Model to integrate with TFS 2012.

  • An external procedure has removed the Operational Issue WITD from the team projects in TFS, and you still want to synchronize with this team project.

  • You are configuring synchronization with a non-English version of TFS.


The Operational Issue work item type can be renamed and customized, but you also need to customize synchronization as described in Integrating Operations Manager with Non-English Versions of Team Foundation Server (TFS) or a Customized Process Model in TFS.

To manually import the Operational Issue WITD file

  1. Locate the correct Operational Issue WITD for your version of TFS on the installation media for Operations Manager in System Center 2012 SP1 in the SupportTools folder. For TFS 2010, the file name is OperationalIssue.xml. For TFS 2012, the file name is OperationalIssue_11.xml.

  2. Use TFS administrator credentials to run the witadmin command-line tool in TFS and import the Operational Issue WITD to each TFS project you plan to use with synchronization.

    Example for TFS 2010: witadmin importwitd /collection: /p:ProjectName /f:OperationalIssue.xml

    Example for TFS 2012: witadmin importwitd /collection: /p:ProjectName /f:OperationalIssue_11.xml

  3. Repeat the previous step for each team project that will be used in synchronization.