Skip to main content

SCM and ticketing

This page lists SCM and ticketing integration updates from 2023 and earlier. For current updates, see SCM and ticketing.

Updates that apply to specific Veracode regions show a region icon.

December 12, 2023​

Veracode Azure DevOps Extension 3.25.0​

This update includes the following improvements:

  • The Flaw Import task and the Upload and Scan task now successfully fail the build when the Fail build if Upload and Scan build step fails checkbox is selected.
  • Adds an option to overwrite the iteration path in work items of imported flaws during the next import.

Veracode Integration for Jira Server 4.5.0​

This update adds historical diagnostics data to the Monitoring and Troubleshooting page.

December 4, 2023​

Veracode GitHub Workflow App​

Veracode has released the Veracode Workflow App that allows you to scan your GitHub repositories with Static Analysis, Software Composition Analysis (SCA), and Container Security. The app uses template workflows in a centralized location that you can apply to all repositories across your organization.

The functionality of the app includes:

  • Automated scans of up to thousands of repositories from one location
  • Static, SCA, and Container Security scans start on developer activity from a single workflow
  • Automated scanning does not require developers to configure workflows for individual repositories
  • Broad language support

You can download the app from the GitHub marketplace. For more information, view the Veracode documentation.

November 1, 2023​

Veracode Integration for Jira Cloud 4.12.0​

This update includes the following changes:

  • The Import Automation page now includes an option for you to retry downloading Detailed Reports that failed to download during import.
  • If your account is in the European region and you select a link in a Jira issue to an application profile, the link now opens the Veracode Platform in the European region.
  • User accounts in the European region now see the correct values for various fields in imported Jira issues.

October 4, 2023​

Veracode Integration for Jira Server 4.4.0​

This update adds support for Jira Server version 9.11.2.

September 26, 2023​

Veracode Azure DevOps Extension 3.24.0​

This update includes the following changes:

  • End of support for Team Foundation Server (TFS).
  • Builds no longer fail when the Fail build if flaw importer build step fails option is cleared and the application name contains special characters.

August 31, 2023​

Veracode Integration for Jira Server 4.3.0​

This update includes the following improvements:

  • The Monitoring and Troubleshooting page now shows details about the last four imports.
  • The Monitoring and Troubleshooting page now includes an option for you to retry downloading Detailed Reports that failed to download during import.

August 16, 2023​

Veracode Azure DevOps Extension 3.23.0​

This update includes the following improvements:

  • You can now add an iteration path to the work item settings in the Flaw Importer task.
  • Adds support for Azure DevOps version 2022 RC2.

August 10, 2023​

Veracode Integration for Jira Cloud 4.11.0​

This update includes the following improvements:

  • If an imported story for an open-source component with vulnerabilities changes projects, the integration now creates subtasks for SCA vulnerabilities in that story under the new project.
  • To avoid failed imports, if the integration encounters errors when it searches for linked Veracode fields, it now skips issue creation for any new findings.

July 14, 2023​

Veracode Integration for Jira Server 4.2.0​

This update fixes an issue where IssueCreatorImpl errors on the Monitoring and Troubleshooting page caused unexpected failures.

July 6, 2023​

Veracode Integration for Jira Server 4.1.0​

This update includes the following improvements:

  • The Import Automation now provides an option that attempts to import any flaws that failed to import. If an import fails, the Import Automation no longer uses the last import date of the failed import.
  • The Troubleshooting page now provides a diagnostic dashboard that shows details about the latest import, including information about any errors.

June 5, 2023​

Veracode Azure DevOps Extension 3.22.0​

This update includes the following changes:

  • The Upload and Scan task now supports the optional parameter scanpollinginterval.
  • You can now configure the Flaw Import task to only import findings from Static Analysis and SCA.
  • Minor security improvements.

May 22, 2023​

Veracode Integration for Jira Cloud 4.10.0​

This update includes the following changes:

  • Findings you import with the Import Automation feature now show the date of the last successful import, instead of the last import.
  • When you configure a Selective Import and select the left/right arrows to switch between pages, the selected flaws are no longer cleared.
  • Minor security fixes.

May 4, 2023​

Veracode Azure DevOps Extension 3.21.0​

This update includes the following changes:

  • Adds support for the lifecyclestage parameter as an optional argument in the Upload and Scan task. This parameter is not supported in YAML.
  • The scan polling interval for the Upload and Scan task is no longer twice the expected default value of 120 seconds.

April 13, 2023​

Veracode Integration for Jira Cloud 4.9.0​

The integration now imports findings from scanned applications with COTS (commercial off-the-shelf) enabled.

March 30, 2023​

Veracode Integration for Jira Cloud 4.8.0​

This version includes the following changes:

  • Adds additional logs for troubleshooting.
  • To ensure your imported flaws are current, the integration re-imports them after you fix any configuration issues.
  • On the Selective Import page, the Flaws Per Page and Next Page options no longer show an error message.

March 27, 2023​

Veracode Azure DevOps Extension 3.20.0​

This version addresses the low severity information disclosure issue detailed in CVE-2023-25722. For more information, go to the Veracode Community.

March 2, 2023​

Veracode Azure DevOps Extension 3.19.0​

This update adds support for both of the following YAML property values:

  • ConnectionDetailsSelection='Endpoint'
  • ConnectionDetailsSelection='Service Connection'

March 1, 2023​

Veracode Azure DevOps Extension 3.18.0​

This update includes the following changes:

  • Changes the YAML property value ConnectionDetailsSelection='Endpoint' to ConnectionDetailsSelection='Service Connection'. When you upgrade to this new extension, you must update your YAML with the new value name.
  • Static Analysis work items now have a Grace Period Expiration field.
  • SCA works items now have a First Found Date field and File Path field for vulnerabilities.
  • The Summary Report now shows a link to the Scan Details page.
  • The extension now fails the build if Development Sandbox scans find SCA vulnerabilities.
  • Builds no longer fail when the Fail build if Upload and scan build steps fails option is cleared, but the application name contains special characters.

January 23, 2023​

Veracode Integration for Jira Supports Jira Server 9​

Veracode Integration for Jira version 4.0.1 adds support for Jira Server 9. This integration no longer supports Jira Server 8.6.0 and earlier.

January 10, 2023​

Renaming the ConnectionDetailsSelection='Endpoint' YAML Property​

In February 2023, Veracode will release a new Azure DevOps Extension that uses the YAML property value ConnectionDetailsSelection='Service Connection' rather than the current value ConnectionDetailsSelection='Endpoint'. When upgrading to this new extension, you must update your YAML with the new value name.

January 5, 2023​

Improved Veracode Azure DevOps Extension​

Veracode Azure DevOps Extension version 3.17.0 includes the following improvements:

  • Renamed the Veracode Analysis Center link to Veracode Platform.
  • The extension no longer fails a pipeline build if it has a policy assessment of Conditional Pass, even if the Fail build if application fails security policy checkbox is selected.
  • Fixed a minor error-handling issue when the build artifact directory is empty.
  • The Flaw Import task now fails the build when importing flaws with an unsupported process template and the Fail build if flaw importer build step fails checkbox is selected.

January 3, 2023​

Improved Veracode Integration for Jira Cloud​

Veracode Integration for Jira Cloud version 4.7.0 now successfully loads the Findings Import page when importing large Jira projects.

December 19, 2022​

Improved Veracode Integration for Jira Server​

Veracode Integration for Jira Server version 3.38.0 includes the following improvements:

  • Jira tickets from imported Static Analysis flaws now show the detected CWEs with a dash instead of an underscore. This CWE format matches the results in the Veracode Platform. For example, CWE_123 is now CWE-123.
  • Jira tickets from imported SCA vulnerabilities now support the Mitigation Status and Mitigation Status Description fields.

December 13, 2022​

Veracode Azure DevOps Extension version 3.16.0 fixes the link on the Veracode Scan Summary tab. The link now opens the scan results in the Veracode Platform instead of the Application page.

November 16, 2022​

Updated Veracode Integration for Jira​

Veracode Integration for Jira version 3.37.0 fixes an issue where the plugin ignores all remaining applications after attempting to import findings from an application with COTS enabled.

October 21, 2022​

Veracode Azure DevOps Extension Now Supports Automatic Deletion of Incomplete Scans​

Veracode Azure DevOps Extension version 3.15.0 adds options for deleting incomplete scans in your pipeline. When configuring the extension, you can add -deleteincompletescan as an optional argument or add -deleteIncompleteScan as a YAML property.

September 22, 2022​

Improved Finding Import Performance for Veracode Integration for Jira Cloud​

Veracode Integration for Jira Cloud version 4.6.0 adds a new filter that only imports findings with new scan data, policy changes, or changes to applied mitigations since the last import.

August 29, 2022​

Veracode Azure DevOps Extension Has Improved Flaw Importer Task​

Veracode Azure DevOps Extension version 3.14.0 includes the following improvements to the Flaw Importer Task.

  • Uses fewer calls to complete flaw imports.
  • Fixes an issue where flaws without comments did not sync or close.
  • Fixes an issue where development sandbox findings did not import.

August 9, 2022​

Veracode Integration for Jira Server Now Retries Downloading the Detailed XML Report​

Veracode Integration for Jira version 3.36.0 fixes an issue where the integration did not create tickets of imported flaws if it could not retrieve the Detailed XML Report. The integration now attempts to retrieve the Detailed XML Report during the next import cycle.

July 20, 2022​

Veracode Azure DevOps Extension Now Supports Importing SCA Vulnerabilities as Work Items​

Veracode Azure DevOps Extension version 3.13.0 updates the Flaw Importer task to support importing Software Composition Analysis (SCA) vulnerabilities as work items.

June 27, 2022​

Improved Finding Import Performance for Veracode Integration for Jira Server​

Veracode Integration for Jira Server version 3.35.0 adds a new filter that only imports findings with new scan data, policy changes, or changes to applied mitigations since the last import.

March 9, 2022​

Updated Azure DevOps Extension​

Veracode Azure DevOps Extension version 3.10.0 includes these changes:

  • TFS 2017 is no longer supported.
  • TFS 2018 support now requires Azure Pipeline Agent 2.196.2 or later.
  • Flaw Importer task can now import custom fields when using custom process templates.
  • Flaw Importer task can now overwrite the area path in work items when importing flaws.

December 10, 2021​

Veracode Integration for CA Agile Central/Rally Now End-of-Life​

  • The Veracode Integration for CA Agile Central/Rally is now end-of-life and no longer supported. The plugin and documentation are no longer available. To avoid potential security vulnerabilities, Veracode strongly recommends that you uninstall this integration. To integrate with other ticketing systems, visit the Veracode Integrations Hub.

June 23, 2021​

Veracode Integration for Jira Supports the Jira Select List Field Type for Multiple Choices​

  • The Veracode Integration for Jira version 3.30.0 adds support for the Select List (multiple choices) field type. You can use this field type to map data from Veracode custom fields or a Veracode Detailed XML report to standard or custom fields in Jira Server issues.

May 18, 2021​

Veracode Integration for Jira Cloud Supports the Select List Field Types​

  • The Veracode Integration for Jira Cloud version 3.7.0 adds support for the Select List (single choice) and Select List (multiple choices) field types. You can use these field types to map data from Veracode custom fields or a Veracode Detailed XML report to standard or custom fields in Jira Cloud issues.

April 30, 2021​

Veracode Azure DevOps Extension Has Renamed YAML Property and Improved Logging​

Veracode Azure DevOps Extension version 3.5.0 includes these changes:

  • For YAML pipelines with the Flaw Importer task, Veracode renamed the optargs property to proxySettings. This new name more accurately identifies the valid values for this property. Ensure you update your pipelines with this new property name.
  • Added logs, with error messages, for invalid or missing values. The errors apply to both standard and YAML pipelines.

April 20, 2021​

Veracode Integration for Jira Supports the Select List Field for a Single Choice​

  • The Veracode Integration for Jira version 3.29.0 adds support for the Select List (single choice) field type. You can use this field type to map data from Veracode custom fields or a Veracode Detailed XML report to standard or custom fields in Jira issues.

February 5, 2021​

Updated Veracode Azure DevOps Extension​

Veracode Azure DevOps Extension version 3.4.0 includes these updates:

  • Use YAML to add Veracode analysis to build pipelines.
  • Use YAML to import findings as work items into Azure DevOps.
  • Include mitigation and annotation comments when importing new findings as work items.
  • Set a timeout to fail a build if Veracode analysis does not complete within a specified time.

November 19, 2020​

Veracode Integration for Jira Cloud Improves Findings Import Options​

The Veracode Integration for Jira Cloud version 3.5.0 includes these improvements:

  • Uses mapped custom fields in the Veracode Platform when assigning issues of imported findings. If Veracode custom fields are not mapped to Jira fields, Jira Cloud assigns the issues to the default assignee for the Jira project.
  • Adds the ability to map Jira Cloud fields to Veracode Platform fields for SCA components and SCA vulnerabilities.

September 30, 2020​

Introducing Veracode for GitHub​

  • Veracode for GitHub enables you to use GitHub Actions for performing static analysis of your application source code from within GitHub. Veracode provides preconfigured GitHub Actions for uploading your code to Veracode for static analysis or running a pipeline scan from within your GitHub development workflow.

September 11, 2020​

Veracode Integration for Jira Cloud Adds Description Field Override Option​

  • The Veracode Integration for Jira Cloud version 3.4.0 adds the global option for overriding the Description field in Jira issues. When importing findings as issues into Jira Cloud, this option replaces any content in the issue Description field with your provided text.

August 13, 2020​

Veracode Integration for Jira Adds Description Field Override Option​

  • The Veracode Integration for Jira version 3.25.0 adds the global option for overriding the Description field in Jira issues. When importing findings as issues into Jira Server, this option replaces any content in the issue Description field with your provided text.

June 25, 2020​

Veracode Integration for Jira Improves Issue Assignment of Imported Findings​

  • The Veracode Integration for Jira version 3.24.0 can now use mapped custom fields in the Veracode Platform when assigning issues of imported findings. If Veracode custom fields are not mapped to Jira fields, Jira Server assigns the issues to the default assignee for the Jira project.

May 29, 2020​

Veracode Integration for Jira Cloud Adds Findings Import Options​

The Veracode Integration for Jira Cloud version 3.3.0 adds these new options for importing findings from Veracode to Jira Cloud:

  • Automatically assign imported findings to a Jira Cloud epic or link them to a related issue.
  • Map string, number, and date/time data types from Veracode fields to text, number, and date/time field types in Jira Cloud. The integration imports the values from the Veracode fields to fields in Jira Cloud issues.

May 19, 2020​

Veracode Azure DevOps Extension Adds New Scan Summary for Multi-Stage Pipelines​

  • The Veracode Azure DevOps Extension version 3.1.0 shows scan results in a new Veracode Scan Summary tab to support multi-stage pipelines.

May 7, 2020​

Veracode Integration for Jira Adds Findings Import Options​

The Veracode Integration for Jira version 3.23.0 adds these new options for importing findings from Veracode to Jira Server or Jira Data Center:

  • Automatically assign imported findings to a Jira epic or link them to a related issue.
  • Map string, number, and date/time data types from Veracode fields to text, number, and date/time field types in Jira. The integration imports the values from the Veracode fields to fields in Jira issues.

April 10, 2020​

Veracode Integration for Jira Supports Jira Server 8.7.x​

  • The Veracode Integration for Jira version 3.22.1 adds support for Jira Server and Jira Data Center 8.7.x.

March 24, 2020​

Veracode Azure DevOps Extension Removes Basic Authentication​

  • The Veracode Azure DevOps Extension version 3.0.0 removes basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.

January 23, 2020​

Updated Veracode Integration for Jira​

The Veracode Integration for Jira version 3.22.0 includes these updates:

  • Removes support for basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.
  • Enhances Jira logging, so that you can more easily read the logs.
  • Improves the performance of importing findings from the Veracode Platform to Jira using custom fields.

January 8, 2020​

Updated Veracode Integration for Jira Cloud​

The Veracode Integration for Jira Cloud version 3.2.0 includes these updates:

  • Adds a new Veracode Integration Severity Mappings page in the Jira Cloud interface for mapping severities from the Veracode Platform to your customized priorities in Jira Cloud.
  • On the Veracode Integration Field Mapping page in the Jira Cloud interface, the Veracode Platform column adds these new options:
  • A Description (overwrite) option to have the content from a selected Veracode Platform field overwrite the Description field in Jira Cloud upon import. If the selected Veracode Platform field is empty, the mapping erases the contents of the Description field in Jira Cloud.
  • An option for mapping Veracode SCA component paths.
  • Removes basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.