BugMojoBugMojo
Get started
How-to

Connect GitHub to BugMojo

Link a BugMojo project to a GitHub repo so you can create issues, connect pull requests, and keep status in sync both ways.

Applies toPlans:FreeProBusinessEnterpriseRoles:AdminWhere:Web app

The GitHub integration lets a captured bug become a real GitHub issue, links the pull request that fixes it, and keeps status agreed across both tools. This guide connects GitHub, maps a project to a repo, creates and links issues, and shows how sync and disconnect work. You need to be an ADMIN or OWNER.

Before you start

Make sure you have the following:

  • An ADMIN or OWNER role in your BugMojo workspace.
  • Access to the GitHub repository you want to use, so you can create a personal access token for it.
  • A BugMojo project that will map to that repository.

Connect the GitHub integration

  1. Open Settings → Integrations in the web dashboard and find GitHub.

  2. Click Connect and enter the Owner and Repository. They match github.com/{owner}/{repo}.

  3. In GitHub, open Settings → Developer settings → Personal access tokens, generate a token with the repo scope, and paste it into BugMojo. If your workspace shows Continue with GitHub, you can authorize in the browser instead.

  4. You return to BugMojo with GitHub showing as Connected.

Map a project to a repository

The connection tells BugMojo which repos it may use; the mapping tells it where a project's bugs should go.

  1. In the GitHub integration panel, click Add mapping.

  2. Pick the BugMojo project, then choose the GitHub repository its bugs should map to.

  3. Save the mapping. That project can now push bugs into the chosen repo.

Create issues and link pull requests

From any bug on a mapped project, open the bug detail page and use the GitHub section in the sidebar:

  • Click Create GitHub issue to open a new issue in the mapped repo. BugMojo carries the summary, repro steps, and a link back to the bug's replay and logs.
  • Already have an issue or a fix in flight? Paste its URL into Link pull request or Link issue to connect it instead of creating a new one.

How two-way status sync works

Once a bug is linked, status flows in both directions. Move the bug from OPEN to IN_PROGRESS in BugMojo and the linked issue advances. On the GitHub side, closing the issue or merging the linked pull request moves the bug toward CLOSED, and reopening the issue can move it back to REOPENED. Neither system falls out of date because you only ever act in one place.

Disconnect GitHub

  1. Go to Settings → Integrations → GitHub.

  2. Remove any project-to-repo mappings you no longer want, or click Disconnect to remove the integration entirely.

  3. Confirm. Future sync and issue creation stop immediately; issues and pull requests already in GitHub are left untouched.

Common questions

Who can connect the GitHub integration?

An ADMIN (or OWNER) connects GitHub in workspace settings and maps it to a project. Developers and QA can then push bugs to the mapped repo, but they cannot change the connection itself.

Does closing a GitHub issue update the bug in BugMojo?

Yes. GitHub sync runs both ways. Close or reopen the linked issue, or merge the linked pull request, and the BugMojo bug advances to the mapped status automatically. You do not update two places by hand.

Can one BugMojo project point at more than one repo?

Each project maps to one GitHub repository at a time. To push bugs into a different repo, change the mapping in settings, or use a separate project for that codebase.

What happens to linked issues if I disconnect GitHub?

Disconnecting stops all future sync and issue creation. Issues and pull requests already created in GitHub stay where they are. BugMojo just no longer updates them or reflects their changes.

Was this helpful?
Updated Jul 10, 2026 · Still stuck? Contact support

Related articles