Bug Reports Delivered as GitHub Issues
Every bug report is created as a GitHub Issue with the screenshot, console errors, device details, and session replay links — formatted and ready to triage.
Callout delivers bug reports directly to your GitHub repository as formatted issues. Each issue includes an annotated screenshot, console error logs, browser and device details, and session replay links. No copy-pasting, no manual issue creation — reports land in your existing workflow automatically.
From report to
issue in seconds.
Connect once. Every report lands in your repo.
Connect your repository
Provide a GitHub Personal Access Token with repo scope and specify the repository where issues should be created. This is a one-time setup in your Callout project configuration.
User submits a bug report
When a user clicks the Callout widget, captures a screenshot, annotates it, and writes a description, the report is sent to the Callout API along with all auto-collected data.
Issue created automatically
Callout uploads the screenshot to GitHub, formats the issue body with all collected data — description, screenshot, errors, device info, replay links — and creates the issue in your repository. Your team sees it immediately.
Bug reports that
fit your workflow.
No Copy-Pasting
Bug reports go directly from the user to your issue tracker. No Slack messages to transfer, no emails to parse, no manual issue creation. The report is the issue.
Rich, Formatted Issues
Every GitHub Issue is formatted with sections for description, screenshot, console errors, device details, and replay links. Your team can triage immediately without requesting more information.
Works with Any Repo
Public or private, personal or organization — Callout works with any GitHub repository. Connect with a Personal Access Token and start receiving issues. No GitHub App to install.
Linear and Jira Too
Not using GitHub? Callout also delivers reports to Linear and Jira with the same rich format. Choose whichever issue tracker your team already uses.
Common
questions.
How does Callout create GitHub Issues from bug reports?
When a user submits a bug report through the Callout widget, the report is sent to the Callout API which creates a GitHub Issue in your repository using the GitHub API. The issue includes the user description, annotated screenshot, console errors, device details, and session replay links — all formatted and ready to triage.
What information is included in the GitHub Issue?
Each GitHub Issue includes: the user-written bug description, an annotated screenshot embedded inline, console error logs, browser and device details (browser, OS, viewport, screen resolution, page URL), and session replay links from PostHog, LogRocket, Hotjar, or FullStory if detected.
Does Callout work with any GitHub repository?
Yes. Callout works with any GitHub repository — public or private. You provide a GitHub Personal Access Token with repo scope, and Callout uses it to create issues in your chosen repository. No GitHub App installation is required.
Does Callout also support Linear and Jira?
Yes. In addition to GitHub Issues, Callout can deliver bug reports to Linear and Jira. The same rich report format — screenshots, errors, device info, and replay links — is delivered to whichever issue tracker your team uses.
Try Callout free — no account required
Bug reports delivered as GitHub Issues. Free forever.
Get Started Free