This table lists the standard fields in Jira and Jira Cloud to which you can map Veracode custom fields on the Veracode to Jira Field Mappings page. The Veracode to Jira Field Mappings page is available with the Veracode Integration for Jira and the Veracode Integration for Jira Cloud.
|Standard Jira field
|User assigned to the issue. The Veracode Integration for Jira uses these criteria when populating the Assignee field in Jira:
|Comma-separated list of component values defined in custom fields in the Veracode Platform. Use this format for each component:
This example defines these components:
comp1: : :
For the default assignee type, use these numeric values:
|Adds the finding description value from the Veracode
detailedreport.xml file and appends it to the existing description in the issue. The Description (overwrite) option replaces the Description field in Jira or Jira Cloud with the value from the selected field in the Veracode Platform. If the Veracode Platform field is empty, the mapping erases the contents of the Description field in Jira or Jira Cloud.
|Issue type, such as story, bug, or epic. If there is no mapping for this field, the integration uses the issue type set in Jira or Jira Cloud.
|Comma-separated list of labels to add to the issue. These labels do not affect any existing labels. During import, the integration removes any spaces between labels and concatenates any strings.
|Original estimate of the work required to resolve this issue. To map this field, you must have Time Tracking configured on the screen.
|User designated as the reporter for an issue. If there is no mapping for this field, the integration uses the reporter specified in Jira or Jira Cloud.
|Time spent working on an issue. The value is based on the Time Tracking setting in Jira or Jira Cloud. You can set the default unit to Minute, Hour, Day, or Week. The integration converts the input long value to the default unit. To map this field, you must have Log Work configured in Jira or Jira Cloud.