GitHub
Auto-open issues
- Auto-open issues from error groups
- Issue composer with context checklist
- PR tracked in repair status
GitLab
Sync issue state
- Issue creation from error groups
- Issue state syncs both ways
- Resolution closes the loop
Jira
Ticket creation
- Ticket creation with full context
- Project and issue-type mapping
- Links back to the error group
Slack
Channel routing
- Per-project channel routing
- Incident opens and closes announced
- Severity-aware notifications
Webhook
Custom endpoints
- JSON payloads to any endpoint
- Fires on error, incident, and uptime events
- Build what we didn’t
Need something else?
The webhook integration carries every event errorgap emits. If you can receive JSON, you can integrate.
Webhook reference →Issue composer
The issue writes itself. You check boxes.
Opening an issue from an error group assembles the body from a context checklist — backtrace, occurrence counts, release, linked incident. Uncheck what the assignee doesn’t need.
- Context checklist controls the issue body
- Works for GitHub, GitLab, and Jira
githubnew issue · ox-coffee/storefrontfrom error group
Stripe::CardError in checkout/charge.rb:81
labels: bug, production · assignee: @mara
☑backtrace + source context
☑occurrence count & first/last seen
☑release · v2.14.1
☑linked incident · INC-241
☐session replay link
issue body assembled from checked context
Repair status
From PR to verified fix.
Once an issue links to an error group, errorgap tracks the repair: the PR, the release that ships it, and a verification window that confirms the error actually stopped.
- PR → release → verification, tracked automatically
- Recurrence during verification reopens the loop
repair status · grp_9f2c41tracked automatically
PR opened#1482 · fix: pass tokenized source to chargemerged
Releasev2.14.2 · deployed 16:08 UTClive
Verificationno recurrence in 24h window14h remaining
Related capabilities