A mapping definition is a collection of settings that describes how AccuSync synchronizes AccuWork and ITS issues. Examples of mapping definition settings include:
|Issue type||You create a mapping definition for each issue type you want to synchronize. You might create one mapping definition for defects and another for tasks, for example.|
|Field mappings||You use field mappings to specify the AccuWork issue fields and ITS issue fields whose data you want to synchronize. For example, you might want to synchronize the content of the AccuWork issue Assigned To field with the content of the Owner field in your ITS. Depending on the allowed values for a given field, and whether those values are the same on both systems, you also might need to create a mapping group. See Mapping Groups for more information.|
|Transformers||AccuSync uses transformers to convert values in one system to different values in the other.
AccuSync includes several predefined transformers, and you can create custom transformers using a Java project installed with AccuSync. See Transformers for more information.
|Synchronization type override||The synchronization type determines whether AccuSync performs a two-way or one-way synchronization. By default, AccuSync uses the synchronization type specified for the synchronization pattern that the mapping definition is associated with. If you want, you can override the synchronization type for individual field mappings. See Synchronization Types for more information.|
|Filters||Filters provide a way for you to control which issues, or types of issues, are synchronized. For example you might create a filter that does not synchronize issues filed against a specific subsystem, or issues submitted by a specific user. You can define filters for both AccuWork and your ITS. See Creating a Mapping Definition Filter for more information.|