You can configure Jira to log the actions that the Veracode Integration for Jira performs. The log messages are located in the standard Jira log.
You can enable logging in the Jira interface and the log4j.properties file. If you enable logging in the Jira interface and restart Jira Server, you must re-enable logging. If you enable logging in the log4j.properties file and restart Jira Server, logging remains enabled.
Jira Cloud does not support logging.
The location of the Jira logs depends on the Jira installation location. For example:
- On Linux:
- On Windows:
C:\Program Files (x86)\Atlassian\Application Data\Jira\log\atlassian-jira.log
To complete this task:
In Jira, select Administration > System > Logging & Profiling.
In the Default Loggers section, select Configure logging level for another package.
In the window, in the Package name field, enter
From the Logging Level dropdown menu, select INFO or DEBUG.
If you want logging to remain enabled after restarting Jira Server, edit the file
Add these two properties to
log4j.logger.com.veracode.jira.plugin = INFO, filelog
log4j.additivity.com.veracode.jira.plugin = false
log4j.logger.com.veracode.jira.plugin, you can enter one of these logging levels:
The Veracode Integration for Jira saves all retrieved findings information. You can review the flaw report XML files to understand the actions the integration performed. Example flaw report locations include:
C:\Program Files (x86)\Atlassian\Application Data\Jira\veracode\flawreportxml