How to Integrate BugMojo with Linear

What this integration does

When a teammate captures a bug with BugMojo, an issue is created in Linear with the title, description, hero screenshot, and a deep link back to the session replay. Comments and status changes sync both ways — close the Linear issue and the BugMojo capture marks resolved automatically.

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 Linear specifically, this means engineering picks up bugs in linear with the session replay one click away — no context-switching.

Before you start

Make sure you have:

• A BugMojo account with admin access (Settings → Integrations is admin-only).
• A Linear 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 Linear API key

In Linear, open Settings → API → Personal API keys → Create new key. Give it a memorable name like 'BugMojo sync' and copy the key — you'll only see it once.

Step 2: Connect Linear in BugMojo

In BugMojo, open Settings → Integrations → Linear → Connect. Paste the API key and select the team + default project where new bugs should land.

Step 3: Pick which fields sync

Choose whether BugMojo pushes priority, labels, and assignees. Default is to push priority + a "bugmojo" label so issues are filterable in Linear.

Step 4: Test the connection

Capture a test bug in BugMojo. Within 5 seconds you should see a new issue appear in Linear's selected project. Verify the deep-link to the session replay works.

Workflows this enables

Beyond the "bug appears in Linear" 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.

• Engineering picks up bugs in Linear with the session replay one click away — no context-switching.
• When dev closes the Linear issue, BugMojo auto-marks the original capture resolved.
• Status changes (Todo → In Progress → Done) sync back to BugMojo for QA-team visibility.

Troubleshooting

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

"Bugs aren't appearing in Linear."

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

"Two-way sync is one-way only." Confirm you've configured the webhook on the Linear side. BugMojo → Linear 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 Linear 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.

Frequently asked questions

What does the BugMojo + Linear integration sync?

How long does setup take?

What permissions does the integration require?

Can I sync only certain bugs to Linear?

Does the integration work for self-hosted BugMojo?

Sources

1. Linear official site — Linear (2026)
2. BugMojo integrations documentation — BugMojo (2026)