GitHub issues sync
Turn on the import and every open issue in your connected repo lands in the Usero inbox next to widget, Slack, and form feedback. Duplicates group by meaning, and a clustered issue can open a GitHub PR you review and merge. Nothing auto-merges.
GitHub issues are a fine place to file a report and a poor place to read a hundred of them. They pile up, the same bug arrives in fifteen wordings under fifteen issue numbers, and support questions sit in the same list as real bugs.
An issue tracker counts issues, it does not tell you which problem recurs. Ten people hit the same broken export and open ten issues, and the only dedup you get is someone manually commenting "duplicate of #142" and closing one, which loses the reporter context every time. There is no voting that scales past the handful of users who already have a GitHub account and know to react, no grouping by meaning, and no single view that merges your repo issues with the feedback arriving from your widget, your Slack, and your forms. So the signal you care about, the theme that twenty reports are circling, stays buried under the issue list, and the backlog grows faster than anyone grooms it. What you want is the issues somewhere that reads them by meaning, puts a count on each theme, and sits next to the change that fixes them.
How it works
Disclosure: I build Usero, so weigh that. You connect a repo once by installing the Usero GitHub App, then turn on Import GitHub Issues in the GitHub section of Settings. Existing open issues import as feedback items, and new issues opened after that are picked up on an ongoing basis, so there is no backfill to re-run for each one. An optional label filter restricts the import to issues carrying the labels you pick (the picker lists the real labels from your repo); leave it empty to import every open issue. Once imported, an issue is feedback like everything else: it runs through the same AI classification and clusters by meaning with your widget, Slack, form, and email feedback, so a bug reported in an issue and the same bug reported through your widget land in one cluster with a count. Then the wedge runs. From a feedback item or a cluster you click Create PR, Usero clones the repo, writes the change on a branch, and opens a pull request. If the feedback came from a GitHub issue, the PR body includes Fixes #NNN so merging the PR closes the original issue. You review the diff and merge it yourself. Usero never merges for you.
An imported issue sits next to feedback from your widget, Slack, forms, and email, and clusters with all of it. A bug reported in a GitHub issue and the same bug reported through the widget collapse into one theme with a count, instead of living in two trackers that never compare notes.
Usero reads "export does nothing", "cannot download my report", and "CSV is broken" across separate issues and recognizes them as one problem. The count turns a wall of issue numbers into a ranked list of what recurs, which is the thing the native issue list will not give you.
New issues opened after you enable the import are pulled in automatically, so you do not re-run a backfill. If you only want issues carrying certain labels (say "bug" or "customer"), set a label filter from the picker that lists your repo labels, and leave it empty to import everything open.
From a feedback item or 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 carries Fixes #NNN, so merging it closes the issue. You review the diff and merge through your own branch protection.
The honest objection
If your issue volume is low and your users are all developers comfortable filing issues, the native tracker may be all you need, and you can skip this. The reason to import is analysis and action that GitHub does not do: clustering by meaning across every feedback source, a count on each recurring theme, and a one-click path from a clustered issue to a reviewable GitHub PR. Usero does not replace your issue tracker; the import is read-in, the issues stay in GitHub, and a merged PR closes the original issue with Fixes #NNN. 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 turn on Import GitHub Issues in the GitHub section of Settings. Existing open issues import as feedback, and new issues opened afterward are picked up on an ongoing basis, so there is no backfill to re-run.
Yes. Set a label filter and the import is restricted to open issues carrying the labels you choose. The picker lists the real labels from your repo. Leave the filter empty to import every open issue.
Yes. An imported issue is feedback like any other source, so it runs through the same AI classification and clusters by meaning with your widget, Slack, form, and email feedback. The same bug reported in an issue and through the widget land in one cluster with a count.
No. The import reads issues into Usero; the issues stay in GitHub untouched. The one write-back path is a pull request: if you open a PR from feedback that came from an issue, the PR body includes Fixes #NNN, so merging that PR closes the original issue.
Yes. From a feedback item or a cluster you click Create PR and Usero clones the repo, writes the change on a branch, and opens a GitHub pull request with a first pass at the fix. You review the diff and merge it through your own branch protection. There is no auto-merge path.
Free tier. No credit card. Two-minute install. The AI opens the PR, you merge it.