Export (0) Print
Expand All

Migrating from ClearQuest

The work item migration converter:

  • Reads the work items from ClearQuest

  • Writes the data into Team Foundation using the Visual Studio Team System work item tracking Web services.

  • Migrates attachments and links.

  • Migrates duplicate work item information.

To write the data into Team Foundation, the converter replays the actions that users performed in the original work item tracking system. For example, if a work item was opened, resolved, and then closed, the converter opens the work item in Team Foundation, resolves it, and then closes and saves the work item every time. The converter preserves the user names and dates of those actions.

You can control how the data is mapped from ClearQuest to Team Foundationthat includes changing the field values and how users are mapped. You specify the settings for the converter by editing the XML files that control how the data is migrated.

The following sections can help you migrate your work items to Team Foundation.

ClearQuest Converter Limitations

Describes limitations of the ClearQuest converter that includes a list of items that are not migrated.

Planning for Work Item Migration

Describes how to plan for a migration from ClearQuest to Team Foundation.

Migrating Work Items

Describes how to migrate work items from ClearQuest to Team Foundation.

After Migrating Work Items

Describes the tasks to do post-migration to make sure a successful migration and troubleshoot migration problems.

CQConverter Command-Line Utility for ClearQuest Database Migration

Describes the CQConverter.exe tool and provides link to topics that detail the commands and options.

The Work Item Tracking Schema

Team Foundation work item tracking schema defines a specific work item type. The schema defines:

  • The fields, field names, and field types on a work item form.

  • The rules associated with a work item. For example, a work item can have a rule that the Opened Date is set to the current date when someone creates a new work item.

  • The list of supported values for a field.

  • Optional/Read-Only/Mandatory characteristics of the fields.

  • Workflow, as in the states the bug can complete; open, resolve, closed.

  • Work item form, the form used to track work items for your project.

See Also

Community Additions

ADD
Show:
© 2014 Microsoft