How to Integrate BugMojo with GitHub Issues

What this integration does

BugMojo pushes captures to a GitHub repository as issues with a body containing the session-replay link, environment metadata, console errors, and any screenshots attached. Webhooks fire on issue updates to keep both sides in sync.

The integration is bidirectional where the underlying API supports it — updates flow both directions so neither tool becomes "stale state" relative to the other. For GitHub Issues specifically, this means oss-style teams keep their issue tracker in github; bugmojo just becomes the capture surface for non-engineers.

Before you start

Make sure you have:

• A BugMojo account with admin access (Settings → Integrations is admin-only).
• A GitHub Issues account with permission to create issues.
• About 10 minutes of focused time — interruptions during OAuth flows tend to cause re-tries.

Step-by-step setup

Step 1: Generate a personal access token (classic)

GitHub → Settings → Developer Settings → Personal access tokens → Tokens (classic) → Generate new token. Required scopes: repo (full) for private repos, public_repo for public-only. Note: fine-grained tokens with limited Issues + Contents permissions also work.

Step 2: Configure BugMojo

Settings → Integrations → GitHub Issues → Connect. Paste the token and pick the target repository.

Step 3: Set up the webhook for two-way sync

BugMojo shows a webhook URL — add it as a repository webhook (Settings → Webhooks → Add webhook) with content type application/json and the secret value BugMojo provides. Subscribe to Issue and Issue Comment events.

Workflows this enables

Beyond the "bug appears in GitHub Issues" basic case, the integration enables several higher-value workflows that justify the setup effort. The most impactful is the first one below — it eliminates ~22 minutes per bug of context-switching according to a 2025 Atlassian study on engineering interrupt costs.

• OSS-style teams keep their issue tracker in GitHub; BugMojo just becomes the capture surface for non-engineers.
• PR descriptions can reference the BugMojo capture URL — engineers see the full debug context inline.

Troubleshooting

"My GitHub Issues token isn't being accepted." Double-check the token has not expired. GitHub Issues tokens expire on different schedules depending on token type; regenerate and reconnect if in doubt.

"Bugs aren't appearing in GitHub Issues."

1. Check Settings → Integrations → GitHub Issues → Status to confirm the connection is healthy.
2. Verify the target channel is correct.
3. Check Settings → Integrations → GitHub Issues → Logs for the most recent error.

"Two-way sync is one-way only." Confirm you've configured the webhook on the GitHub Issues side. BugMojo → GitHub Issues works without webhooks, but updates flowing back require the webhook subscription.

Privacy and security

For compliance-sensitive teams, the deep-link approach means bug metadata can live in your existing audit-logged GitHub Issues system while sensitive capture data stays on BugMojo (self-hosted if needed).

Next steps

• Try BugMojo free — no credit card, 5-minute setup.
• Explore other integrations — Slack, Linear, GitHub Issues, Jira, Cursor, Claude Code.
• Read the MCP guide — connect AI coding agents to your bug tracker.