All Issues

The All Issues view lists every issue found in a report and helps teams move from high-level summary to detailed triage.

The rest of this page walks through using All Issues to inspect findings and interpret grouping. It also explains how to decide whether to fix, hide, or escalate each item so your triage flow stays consistent across reviewers.

What you can do here

inspect issue-level detail
review needs-review findings
understand which guideline each issue maps to
switch grouping based on the report structure
take actions such as hide, restore, export, or report a bug

When to use this

Use this view when you need issue-level depth rather than summary statistics.

How to triage in All Issues (onboarding)

Open a report from the dashboard, then choose All Issues.
Sort or filter by severity, rule, URL, or state (available controls depend on scan type).
Click an issue to read the element context, selector hints, and remediation text where the product provides it.
For noisy or accepted exceptions, use Hide and Restore Issues so future runs respect your decision—document the reason for auditors.
For engineering work, use Bug Report or your Jira / Slack integration so the finding carries screenshots and deep links.
Re-run the same URL or flow after a fix and compare issue counts or use Passed Test Cases if enabled for a fuller before/after story.