C. JIRA Configuration Reference : Mapping Definitions Summary

Mapping Definitions Summary
The following table summarizes the mapping definitions included in the default configuration for JIRA. Details for individual mapping definitions follow this table.
If you create a new AccuSync Configuration (as opposed to using the default configuration for JIRA), you need to create one mapping definition for each type of issue (defect, enhancement, 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.
basic
Required Field Mappings
Field Mappings
JIRA Versions Field
The “versions” field in JIRA is not included in the default mapping definition, but can be set up in your mapping definitions. See Creating Mapping Definitions for more information.
The “versions” field can be defined as Choose or Text type. If the version is a combination of more than one version, the combination should be set up as comma separated in the AccuWork schema as shown in the following example.
If the field is a text field and the version is a combination of more than one version, the end user should be instructed to enter the combined versions as comma separated. For example, when entering the combined versions in AccuWork, the user types: version1, version2 as shown in the following example.
If the user enters a version in AccuWork that does not exist in JIRA, that version will be created in JIRA when the issues are synchronized.
If the user enters a version in JIRA that does not exist in AccuWork, that version will not be shown when the issue is displayed in AccuWork. However, that version will appear in the .xml file (if the accurev xml command is used to “get” the issue).
If the user fails to separate combined versions with a comma (version1 version2), a version will be created in JIRA with that name (version1 version2).
basicCpk
Required Field Mappings
Field Mappings
DefectMapping
Required Field Mappings
Inherited from basic.
Field Mappings
Inherited from basic.
CpkDefectMapping
Required Field Mappings
Inherited from basicCpk.
Field Mappings
Inherited from basicCpk.
TaskMapping
Required Field Mappings
Inherited from basic.
Field Mappings
Inherited from basic.
CpkTaskMapping
Required Field Mappings
Inherited from basicCpk.
Field Mappings
Inherited from basicCpk.
NewFeatureMapping
Required Field Mappings
Inherited from basic.
Field Mappings
Inherited from basic.
CpkNewFeatureMapping
Required Field Mappings
Inherited from basicCpk.
Field Mappings
Inherited from basicCpk.
ImprovementMapping
Required Field Mappings
Inherited from basic.
Field Mappings
Inherited from basic.
CpkImprovementMapping
Required Field Mappings
Inherited from basicCpk.
Field Mappings
Inherited from basicCpk.
SubTaskMapping
Required Field Mappings
Inherited from basic.
Field Mappings
CpkSubTaskMapping
Required Field Mappings
Inherited from basicCpk.
Field Mappings
Inherited from basicCpk.

Micro Focus