Why does my findings export include only some of my findings?

Why this happens

The API describes the issue export as "Export issues as JSON or CSV with filters", and it needs the issue:export permission. The Issues list also hides some triage statuses by default, so what you see may already be a subset. At capture time, the default view showed 136 rows.

How to fix it

1. Empty the Search findings by title or location... box.
2. Set severity, confidence, class and target back to the "All" choices.
3. Press the first chip so it reads Hiding and unselect every status you want to include.
4. Click Export CSV or Export JSON, then count the rows.
5. If rows are still missing, ask an admin whether your group scope covers those targets.

Scope matters as well. A token and a user only see the targets their groups cover. So two people can export different counts from the same workspace.

Still not working?

The capture did not run an export, so this guide cannot say which on-screen filters the buttons pass on. Treat the clean-list approach as the safe route. Compare with the Dashboard remediation counts for a quick check. Read how to export findings to CSV, why findings are missing from Issues and what to do if you cannot export. If counts still differ, tell us through the contact page.

Related questions

• How do I export findings to CSV?
• How do I export findings as JSON?
• How do I hide fixed and false-positive findings from the Issues list?
• Why can't I export findings?
• Why are some findings missing from my Issues list?

Full tutorial

How to export vulnerability findings to CSV or JSON

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre