GitHub issue sync
Issues in your repo become feedback in the Usero inbox, next to widget, Slack, form, and email feedback. Any feedback item can become a GitHub issue with one click. Close the issue and the feedback resolves; resolve the feedback and the issue closes. One card holds the whole setup.
The feedback tool and the issue tracker drift apart within a week. A bug gets fixed in GitHub and the feedback item sits open in the inbox. A request gets resolved in the inbox and the issue an engineer filed from it stays open in the backlog. Someone ends up reconciling the two lists by hand, and then stops.
Most "GitHub integrations" in feedback tools push one way. They create an issue from a post and forget about it, so the two systems agree for exactly as long as nobody touches either one. Import is rarer still, and without it the bugs your developers file directly in GitHub never sit next to the reports arriving from users. The cost is a slow tax: the PM checks GitHub before answering a customer, the engineer checks the inbox before closing an issue, and every so often a user is told a bug is open when it shipped a week ago. What you want is a link that goes both ways and carries the status with it, so either side can close the loop and the other side hears about it.
How it works
Disclosure: I build Usero, so weigh that. You install the Usero GitHub App on a repo once. From then on the GitHub card on your Integrations page is the whole control panel: the repo, one sentence that sets the direction ("Sync both ways between GitHub and Usero", with GitHub to Usero only, Usero to GitHub only, or Off as the other choices), a label filter, the synced count, and a short Recent list of what moved. Turning the sync on runs the backfill straight away, so existing issues land in the inbox without a separate step, and new issues arrive on an ongoing basis after that. In the other direction every feedback item gets a Create issue button that files a GitHub issue and links it. Status follows both ways for every linked issue, whether it was imported or created: closing an issue resolves its feedback, and resolving feedback closes its issue. Comments do not sync. The pull request path is still there: from a feedback item or a cluster you can click Create PR, and Usero opens a GitHub PR you review and merge yourself. Usero never merges for you.
Turn the sync on and open issues in the connected repo land in the inbox, backfill included. Set a label filter (the picker lists your repo labels) to bring in only "bug" or "feedback", or leave it empty for every open issue. Imported issues run through the same AI classification and cluster with widget, Slack, form, and email feedback.
Every feedback item gets a Create issue button. Click it and Usero files a GitHub issue in your repo and links the two, so the engineer gets the report in the tracker they already watch and the feedback item shows the issue number and its state. If you would rather not click, the outbound half of the direction sentence can be set to create issues automatically for every new feedback item, or for bugs only, once the AI has classified it. The default is manual.
Close or reopen an issue in GitHub and the linked feedback resolves or reopens. Resolve feedback in Usero and its linked issue closes. It works the same for an issue that was imported and one you created from feedback, so nobody reconciles the two lists by hand.
The GitHub card is the whole setup: repo, direction, labels, count, and a three-line Recent list of real events, each ending in the direction it travelled. Direction is a single setting: both ways, GitHub to Usero only, Usero to GitHub only, or off.
The honest objection
If your issue volume is low and every reporter is a developer with a GitHub account, the native tracker may be all you need, and you can skip this. The reason to link is that GitHub only hears from people who file issues. Feedback from your widget, Slack, forms, and email never reaches it unless someone copies it over. With the sync on, that feedback can become an issue in one click, the developer bugs filed straight into GitHub cluster with the user reports, and closing on either side closes the other. The issues stay in GitHub, and comments do not sync, so the tracker remains the place engineers talk. If you only want a list to triage by hand, the native issues view is fine and you do not need this.
FAQ
Install the Usero GitHub App on the repo, then open the GitHub card on your Integrations page and set the sentence to "Sync both ways between GitHub and Usero". Existing open issues backfill into the inbox immediately, and new issues arrive on an ongoing basis after that.
Yes. Set a label filter on the GitHub card and only open issues carrying the labels you choose come across. The picker lists the real labels from your repo. Leave the filter empty to sync every open issue.
Yes, when the direction includes Usero to GitHub. Resolving a feedback item closes every GitHub issue linked to it, whether the issue was imported or created from that feedback. Reopening an issue in GitHub reopens the feedback.
Yes. Under the direction sentence, "Usero to GitHub" is a choice: create issues manually, automatically for every new feedback item, or automatically for bugs only. Manual is the default. Automatic creation runs after the AI classifies the item, so the bugs-only option waits for that classification. Status sync for a created issue is automatic whichever option you pick.
Yes. The direction is one setting on the GitHub card: both ways, GitHub to Usero only, Usero to GitHub only, or off. Pick GitHub to Usero only if you want issues in the inbox but do not want Usero writing to your repo.
No. The sync carries the issue itself and its open or closed state in both directions. Comments stay where they were written, so GitHub remains the place engineers discuss the fix.
Yes. From a feedback item or a cluster you click Create PR and Usero opens a GitHub pull request with a first pass at the fix. When the feedback came from an issue, the PR body includes Fixes #NNN, so merging it closes the issue. You review the diff and merge it yourself. There is no auto-merge path.
Free tier. No credit card. Two-minute install. The AI opens the PR, you merge it.
Keep reading