Issue trackers
Send Bugpot reports to GitHub
Available from 1 October 2026The GitHub integration will create issues in the repository you pick, apply labels for issue type and priority, and reopen or close the Bugpot report when the issue does, so the loop actually completes.
Bugpot × GitHub
Turn every triaged report into a GitHub issue with labels, the environment and a link to the annotated screenshot.
Status pills flow both ways.
How the sync will work (from 1 October 2026)
Two-way sync, not a fire-and-forget webhook
From 1 October 2026, Bugpot will write the report into GitHub and then watch for changes coming back (status, comments and closes) so the two systems stay in step without anyone re-typing anything. Until then, the same payload rides on a signed webhook.
Every “Outbound” / “Inbound” behaviour on this page describes how the sync will behave from 1 October 2026.
Outbound
Bugpot → GitHub
New reports become issues in the repository you pick, with labels for priority and issue type, the environment as a table, and console errors as a code block.
Inbound
GitHub → Bugpot
Closing or reopening the issue moves the Bugpot report to whichever status you mapped it to.
Field map
What lands where
Every Bugpot field has a home in GitHub. The defaults are sensible; you can remap any of them from the workspace settings if your setup names things differently.
| Bugpot field | GitHub field |
|---|---|
| Title | Issue title |
| Description | Issue body (Markdown) |
| Reporter name + email | Attributed at the top of the body |
| Environment block (browser, OS, viewport, URL) | Markdown table in the body |
| Console errors | Fenced code block in the body |
| Annotated screenshot | Linked back to Bugpot (GitHub cannot take an upload over its API) |
| Priority | Label |
| Issue type | Label |
| Status | Open or closed, whichever you map it to |
Setup
Five steps, about five minutes
The whole thing runs through OAuth, so you don’t paste tokens, and Bugpot only requests the scopes it needs to create issues and read status changes.
- 1
In Bugpot, open Settings → Integrations and click Connect GitHub.
- 2
Authorise Bugpot to read and write to your GitHub workspace via OAuth.
- 3
Pick the repository that each Bugpot workspace should push to. You can override per issue type.
- 4
Map Bugpot statuses to your GitHub statuses so the two-way sync will know what "resolved" means.
- 5
Send a test report from the widget and confirm it lands in GitHub with the screenshot attached.
Also in Issue trackers
Other integrations in this category
Wire Bugpot up to GitHub in five minutes
The integration is available on every plan. Wire it up during the free trial.