GitHub
Issues are a good record of what's wrong and a poor record of what you're doing about it this week. Connect a repository and its open issues appear beside your tasks, ready to be pulled into the plan without being copied out of GitHub.
What you get
- Connect github.com with OAuth — no token to generate or paste.
- Mirror the open issues from any repository you can access.
- Drag an issue onto a board lane and it's tracked as work, still linked to the source.
- The link back to the original issue stays on the card, so context is one click away.
- Issues stay in sync as they're opened and closed upstream.
Why mirror instead of import
A one-off import turns an issue into a copy that is wrong the moment someone comments on the original. Mirroring keeps the issue where it belongs — in the repository, visible to contributors who will never log into a planning tool — while giving you a card you can prioritise, schedule and assign.
The practical effect is that your board can hold both kinds of work at once: the issues your users filed, and the things you have to do that were never going to be a GitHub issue.
One click, because OAuth
GitHub is the one provider here that connects over OAuth rather than a pasted token, so setting it up is a redirect and an approval. The connection targets the public github.com API; GitHub Enterprise Server is not currently supported.
Setting it up
Create an account, then find it under Settings → Integrations → GitHub. Every connection is part of the single Pro plan at $4.99 per month — there is no per-integration pricing and nothing here is an upgrade.
Questions
Does connecting GitHub change anything in my repository?
Mirroring only reads. Issues, labels and comments in the repository are untouched by the act of putting them on a board.
Do I need to give access to every repository?
No. You authorise the connection and then choose which repositories to mirror. Repositories you don't link are not read.
Does it work with GitHub Enterprise Server?
Not currently — the GitHub connection targets the public github.com API. If you self-host your code, the GitLab and Gitea connections both accept a custom host and will work against your own instance.
What happens when an issue is closed upstream?
The mirrored issue reflects its upstream state, so work closed in GitHub stops showing as open on your board.