Issues
Triage, categorize, and track problems found by Canary.
Issues
Issues are problems discovered by Canary during automated testing. Each issue represents a potential bug, broken functionality, or user experience problem found on your web application.
Issue Lifecycle
Issues follow a simple workflow:
- Open - Newly discovered issue awaiting review
- Fixed - The issue has been addressed in your application
- Verified - Canary has confirmed the fix works
- Closed - Marked as not-a-bug or won't fix
You can also archive issues to remove them from the default view without deleting them.
Severity Levels
Issues are automatically assigned a severity based on their impact:
| Severity | Description |
|---|---|
| Critical | Application crashes, data loss, or security vulnerabilities |
| High | Major functionality broken, blocking user workflows |
| Medium | Partial functionality issues, workarounds available |
| Low | Minor cosmetic issues, edge cases |
Issue Categories (Labels)
Admins can create custom categories to organize issues by team, feature area, or type. Categories help route issues to the right people and track patterns.
To manage categories, go to Settings > Issue Labels.
Evidence & Reproduction
Each issue includes evidence to help you understand and reproduce it:
- Screenshots - Visual capture at the moment of failure
- Browser traces - Network requests, console logs, and timing data
- Steps to reproduce - The exact actions that triggered the issue
- Environment details - Browser, viewport, and test configuration
Filtering Issues
Use the filters at the top of the issues page to narrow down:
- Severity - Filter by critical, high, medium, or low
- Status - Show open, fixed, verified, or all issues
- Property - Filter by which property (website) the issue was found on
- Category - Filter by custom labels
- Credential - Filter by which login context was used
- Date range - Filter by when the issue was last seen
- Search - Full-text search across issue titles and descriptions
Bulk Actions
Select multiple issues to perform bulk actions:
- Archive - Remove from default view
- Export - Download as CSV for reporting
Jira Integration
If you've connected Jira, you can create tickets directly from issues. The Jira ticket will be linked to the Canary issue and kept in sync.
See Jira Integration for setup instructions.
Best Practices
- Triage regularly - Review new issues daily to catch problems early
- Use categories - Organize issues by team or feature for better routing
- Verify fixes - Run tests after deploying fixes to confirm resolution
- Archive, don't delete - Keep a record of past issues for trend analysis