How to export issues to CSV or JSON
From the issue view, there are several ways to export issues to a file (CSV/JSON):
- Export an individual issue.
- Batch export by manually selecting multiple issues.
- Batch export by filtering.
- Export all.
See Ways to triage issues in Polaris for details about these selection methods.
Issue export properties
Property (CSV) | Property (JSON) | Description |
---|---|---|
Issue Type | issueType | The type of issue detected. |
Severity | severity | The severity of the issue (Critical , High , Medium , Low , or Informational ). |
Location | location | The URL where the issue is detected (for issues captured in DAST tests), the path to the file in which the issue is detected (for issues captured in SAST tests), or the name of the component in which the issue exists (for issues captured in SCA tests). |
File Name | fileName | The name of the file in which the issue is detected, if available. |
Tool Type | toolType | The type of test that detected the issue (DAST , SAST , or SCA ). |
Triage Status | triageStatus | The triage status selected when the issue was triaged most recently (To Be Fixed , Dismissed (Intentional) , Dismissed (False Positive) , Dismissed (Other) ), or Not Triaged . |
Fix-By | fixByDate | The issue's fix-by date, if available. |
CVE | cve | The Common Vulnerabilities and Exposures (CVE®) code for the issue, if available. |
BDSA | bdsa | The Black Duck® Security Advisory (BDSA) code for the issue, if available. |
CWE | cwe | The Common Weakness Enumeration (CWE™) code for the issue, if available. |
Application | application | The application in which the issue was detected. |
Project | project | The project in which the issue was detected. |
Branch | branch | The branch in which the SAST or SCA issue was detected. |
Link | link | An absolute link to the issue's details in Polaris. |