Troubleshooting Ticketing Integrations

Veracode APIs

This section helps you remedy common problems and understand how better to use Veracode ticketing integrations.

Ticketing Integration Issue Solution
Veracode Integration for CA Agile Central I receive this message: java.io.IOException: HTTP/1.1 404 Could not determine Web Services Version from 'v2.0https:'. Enter the project ID as a number only. Agile Central Rally project URLs in the browser may include letters. For example, if the project URL is https://rally1.rallydev.com/#/278365550456d/dashboard, then the project ID is 278365550456.
Veracode Integration for Jira I cannot install or configure Veracode Integration for Jira. You need the Jira administrator role to install and configure Veracode Integration for Jira.
Veracode Integration for Jira I installed Veracode Integration for Jira but it is not working. Ensure the API user has the Results API user role assigned. Then, for Veracode Integration for Jira, Associate Veracode Fields with Project Screens in Jira, or for Veracode Integration for Jira Cloud, Associate Veracode Fields with Project Screens in Jira Cloud.
Veracode Integration for Jira If you need to troubleshoot any issues, enable debug logging in Jira.
The location of the Jira logs depends on the Jira installation location. For example:
  • On Linux: /opt/atlassian/jira/logs/catalina.out
  • On Windows: C:\Program Files (x86)\Atlassian\Application Data\Jira\log\atlassian-jira.log
Enable Logging in Jira and set the logging level to DEBUG. After completing any debugging, ensure you change the logging level from DEBUG back to the logging level, such as INFO, and restart Jira.