GitLab
The GitLab connection works against gitlab.com and against instances you host yourself — the host is yours to set, so a GitLab running inside your own network is a first-class citizen rather than an edge case.
What you get
- Point it at gitlab.com or any self-hosted GitLab you can reach.
- Connects with a personal access token carrying the api scope.
- Mirror open issues from any project the token can see.
- Drag an issue onto a lane to plan it, with a link back to the original.
- Paginates properly, so large projects come through completely.
Which token scope, and why that one
Create a personal access token with the api scope. The narrower read_api scope is enough to mirror issues but not to create them, so the wider scope is what lets the same connection work in both directions rather than being read-only.
Tokens are stored encrypted and are only ever used to talk to the host you configured. You can revoke one from GitLab at any time; the connection then stops working and no data already on your board is affected.
Self-hosting is the normal case here
Set the host when you create the connection — gitlab.com is only the default. The API is reached at the standard /api/v4 path on whatever host you give, so a GitLab at git.your-company.com needs nothing beyond being reachable from the internet.
Setting it up
Create an account, then find it under Settings → Integrations → GitLab. 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 it work with self-hosted GitLab?
Yes, and it's the case the connection was built around. You set the host yourself; gitlab.com is just the default value in the field.
Which token scope does it need?
The api scope. read_api is sufficient for mirroring issues but not for creating them, so api is what keeps the connection usable in both directions.
Why a token instead of OAuth like GitHub?
Because the host is not fixed. An OAuth app has to be registered per instance, which would mean an administrator setting one up on every self-hosted GitLab. A personal access token you create yourself works everywhere without involving anyone.