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).