Issues — Review, Fix & Verify
Issues are the core feedback loop. Review AI-discovered findings, triage them, link fixes to code, and verify closures automatically through re-exploration.
WORKFLOW
From discovery to verified fix
Review findings from exploration
After an exploration run, the dashboard shows all issues discovered. Each issue includes a screenshot, console logs, network request data, and an AI-generated description explaining what was found and why it may be a problem.
Issues are grouped by severity (critical, high, medium, low, info). Filter by category, page URL, or status. Click any issue to see full details including reproduction steps, affected flows, and historical occurrences across multiple exploration runs.
Triage — assign severity and category
Review each issue, adjust its severity rating if needed, and categorize it as a bug, visual regression, accessibility issue, false positive, or performance concern.
You can mark an issue as a false positive to dismiss it, or leave it for team review. Issues synced to Jira will reflect severity and category changes automatically. Use bulk selection to apply changes to multiple issues at once.
Link issues to code and track fixes
Each issue can be linked to a specific commit or pull request in your repository. When a fix is pushed, the issue status updates automatically via GitHub webhook integration.
Add references to code using the issue comment thread. Tag team members with @mentions to assign ownership. The issue detail page includes a timeline showing every status change, comment, and linked code reference.
Verify the fix via re-exploration
After marking an issue as fixed, trigger a re-exploration or wait for the next scheduled run. If the issue no longer appears, it closes automatically. If it persists, the status reverts to open with updated evidence.
You can configure auto-close rules — an issue closes automatically after N consecutive clean runs. This reduces manual verification effort while ensuring regressions are caught. All verification history is preserved in the issue timeline.
ACTIONS
What you can do with issues
Change severity
Assign or update severity level (critical → low)
Mark as false positive
Dismiss issues that are not real bugs
Assign to team member
Ownership assignment via @mentions
Link to GitHub commit/PR
Track the fix back to source code
Sync to Jira
Push issue to Jira with all evidence attached
Add comment
Discuss findings with your team inline
Export evidence
Download screenshots, logs, and HAR files
View history
Full timeline of status changes and re-explorations