Issues
Runtime/Repo/Behavior/Visual tabs, status filters, issue detail overlay, Resolve/Ignore/Mute, linked replays, and beginner triage workflow.
What is an Issue?
An Issue is a bucket of similar errors (a fingerprint) so you fix one problem instead of reading thousands of raw events.
Route: /projects/:id/issues
Query params: ?tab=runtime|repo|behavior|visual · ?issue=:id · ?status=… · plus shared filters
Tabs (top of Issues)
| Tab | URL | Purpose |
|---|---|---|
| Runtime | default (often omits tab) | Live product errors from the SDK |
| Repo | ?tab=repo | Static/repo scan findings (GitHub) |
| Behavior | ?tab=behavior | Behavioral friction issues |
| Visual | ?tab=visual | Visual issues |
When you open an issue, the product can sync the tab from origin (behavioral→Behavior, visual→Visual, static→Repo, runtime→Runtime).
Runtime tab — list controls
Subviews: Dashboard | List
Filters:
| Control | Values / notes |
|---|---|
| Status | all / open / resolved / ignored / muted — default is open |
| Type | All / Unhandled / Handled |
| Environment | e.g. production |
| Release | Version string from SDK |
| Search | Placeholder Title, culprit, route… |
Empty states
- SDK not connected: No issues yet · Install Human Behavior · More options → View demo, Book a call
- Filtered empty: No issues match this search / No issues match these filters
Repo tab
- Empty CTA: Connect GitHub to scan your repo · Connect GitHub
- Repo select: All connected repos
- Scan button; banner Scanning :repos…
Behavior / Visual tabs
Status filter + search (Friction, route…).
Issue detail overlay (?issue=)
Metrics: Affected users, First seen, Last seen
Actions:
| Button | Meaning |
|---|---|
| Resolve | Mark fixed |
| Ignore | Do not prioritize |
| Mute | Hide from Open list (Sentry-style — find again under Status → Muted/All) |
Sections you may see:
Events over time, Tags, Severity breakdown, User / session, Session replays, Related issues, Reproduction steps, Stack trace, Breadcrumbs
Also: Copy a permalink with the correct Issues tab, Close
Jump to replays
Use Session replays links — they typically open Replays scoped with ?issue=.
Beginner triage workflow
- Keep Status = open.
- Sort/scan by recent / high user impact.
- Open issue → read stack (upload source maps if minified).
- Open a linked replay — watch the minute before the crash.
- Resolve when fixed in a release; confirm in Releases.
SDK requirements for useful Issues
- Error capture enabled (defaults /
captureException) - Prefer setting
release+environmentin init - Upload source maps for readable stacks
See Error monitoring.