Mapping Definitions Summary

The following table summarizes the mapping definitions included in the default configuration for ClearQuest. Details for individual mapping definitions follow this table.

If you create a new AccuSync Configuration (as opposed to using the default configuration for ClearQuest), you need to create one mapping definition for each type of issue (request, task, and so on) you want AccuSync to synchronize. Separate mapping definitions must be created to manage change package information for each type.

The basic mapping definition is optional; however, if you choose not to create it, all of the field mappings it defines must be created manually for every mapping definition. See Base Mapping Definitions for more information.

Note that you can name these mapping definitions as you choose, but if you change them, make sure you do so throughout your AccuSync Configuration.

Mapping Definition Name	Inherits this Mapping Definition	AccuWork Issue Type	ClearQuest Issue Type
basic	--	--	--
RequestMapping	basic	Request	ALMRequest
TaskMapping	basic	Task	ALMTask

basic

Required Field Mappings

AccuWork Field	ClearQuest Field
cqKey	AccuWorkKey
cqLink	AccuWorkIssueLink

Field Mappings

AccuWork Field	Type	ClearQuest Field	Type	Synchronization Type
assignedTo	User	Owner	reference	two-way
description	Text	Description	multilineString	two-way
project	Text	project	string	two-way
securityPolicy	Text	SecurityPolicy	reference	two-way
shortDescription	Text	Headline	string	two-way
state	Choose	State	string	two-way

RequestMapping

Required Field Mappings

Inherited from basic.

Field Mappings

AccuWork Field	Type	ClearQuest Field	Type	Synchronization Type
severity	Choose	Severity	reference	two-way

TaskMapping

Required Field Mappings

Inherited from basic.

Field Mappings

AccuWork Field	Type	ClearQuest Field	Type	Synchronization Type
priority	Choose	Priority	reference	two-way
request	Text	Request	reference	two-way