What platforms does GitGumbo support?

GitGumbo works with GitLab.com and GitHub.com. You sign in with your existing account using OAuth, and can also add personal access tokens (PATs) for additional accounts or to enable features that require write access. Self-hosted GitLab and GitHub Enterprise Server are not supported yet.

How does GitGumbo detect stale merge requests?

GitGumbo tracks the last activity on each merge request and flags any that have been idle for three days or more. It also surfaces MRs with unresolved review threads, merge conflicts, and failing pipelines.

What data does GitGumbo access?

GitGumbo reads your open merge requests, their statuses, pipelines, labels, and review threads for the projects you explicitly add. It does not access your source code, commit contents, or any data from projects you haven't added.

Can I use GitGumbo with a self-hosted GitLab instance?

Not yet. GitGumbo currently connects to GitLab.com and GitHub.com only, and there is no way to point it at a self-hosted GitLab instance or GitHub Enterprise Server. Support for self-hosted instances is on the roadmap.

Is my data shared with other users?

Your data is shared only within the firms you belong to. A firm is a shared workspace — everyone in it sees the same boards and projects. If you work solo, you get your own private firm that no one else can access, and your data is never shared with users outside your firms.

Can my team share a board?

Yes. GitGumbo organizes work into firms — shared workspaces that own boards and members. Owners and admins invite teammates by email or username from Firm settings, and invitees join automatically the next time they sign in (no separate email step). Everyone in the firm sees the same projects and boards. Each member has a role — owner, admin, or member. You can belong to more than one firm and switch between them from the firm switcher, and billing is handled per firm.

What is the kanban board view?

The board view organizes your issues into columns, with each card showing its linked merge requests and their status. Out of the box, GitLab projects mirror your own board's lists — whether those are labels, statuses, people or milestones — and GitHub projects use Stage:: labels; or you can switch to Your columns and define them yourself. Dragging a card writes the change back to GitLab or GitHub, and what it writes depends on what the column means: a label, an assignee, a milestone, or — on GitLab — a work-item status. GitLab projects require a PAT with api scope for this.

Does GitGumbo understand GitLab's Status field?

Yes. GitLab 18.4 gave work items a native Status — To do, In progress, Done — intended to replace using labels to track lifecycle. GitGumbo syncs it, shows it on every card, and builds your columns from it: a board whose lists are statuses is mirrored as it stands, so a team that has moved off labels needs to change nothing. Dragging a card between status columns writes the new status back. The field is available on every GitLab tier, not just Premium. This one is GitLab-only: GitHub has no equivalent.

Can I cap how many issues sit in a column?

Yes. Give a column a WIP limit and its header counts against it — 7/5 — turning amber when you reach the limit and red when you go past it. It is a warning, not a wall: GitGumbo never blocks the drag, matching GitLab's own behaviour, because a board that refuses your work just gets worked around. The ratio hides while a filter is active, since a filtered count would be measuring something else.

Does the board show milestones and due dates?

Every card shows its milestone, on both providers. Due dates are GitLab-only — GitHub issues don't have one — and appear as a chip that turns amber within three days of the date and red once it has passed. You can filter the board to a single milestone, or flip on the Overdue toggle to see only what is late.

Can I sort issues within a column?

Yes. Each column has its own sort control. You can sort by idle time, recently updated, oldest first, or MR creation date. Click the same option again to reverse the direction. Your sort choice is remembered across sessions.

What are 'In Review' automations?

In Review automations are per-project actions that fire when you drag an issue into an In Review column. GitGumbo can automatically mark draft merge requests as ready, assign team members to the issue, and add reviewers to the linked MRs. You can configure these in the Settings page for each project.

Can I connect multiple accounts?

Yes. In addition to signing in with OAuth, you can add personal access tokens (PATs) in Settings to connect extra accounts for the same provider. This is useful if you work across multiple GitLab instances or GitHub organizations. Each token is encrypted at rest.

Frequently asked questions

Common questions about GitGumbo and how it works.

What platforms does GitGumbo support?: GitGumbo works with GitLab.com and GitHub.com. You sign in with your existing account using OAuth, and can also add personal access tokens (PATs) for additional accounts or to enable features that require write access. Self-hosted GitLab and GitHub Enterprise Server are not supported yet.
How does GitGumbo detect stale merge requests?: GitGumbo tracks the last activity on each merge request and flags any that have been idle for three days or more. It also surfaces MRs with unresolved review threads, merge conflicts, and failing pipelines.
How often does GitGumbo sync my data?: On Pro, GitGumbo registers webhooks with GitLab and GitHub — where the connected account has permission to create them — so most changes show up within seconds. A background sync always runs automatically as the baseline (and is the only sync mechanism on Free), catching anything webhooks miss. Syncs are incremental — if nothing has changed, the overhead is very low. You can trigger a manual sync at any time from the board view (subject to a brief cooldown), and the last sync timestamp is always visible so you know how current your data is. See Real-time updates for what webhooks need and how to fix one that couldn’t be set up.
What data does GitGumbo access?: GitGumbo reads your open merge requests, their statuses, pipelines, labels, and review threads for the projects you explicitly add. It does not access your source code, commit contents, or any data from projects you haven't added.
Can I use GitGumbo with a self-hosted GitLab instance?: Not yet. GitGumbo currently connects to GitLab.com and GitHub.com only, and there is no way to point it at a self-hosted GitLab instance or GitHub Enterprise Server. Support for self-hosted instances is on the roadmap.
Is my data shared with other users?: Your data is shared only within the firms you belong to. A firm is a shared workspace — everyone in it sees the same boards and projects. If you work solo, you get your own private firm that no one else can access, and your data is never shared with users outside your firms.
Can my team share a board?: Yes. GitGumbo organizes work into firms — shared workspaces that own boards and members. Owners and admins invite teammates by email or username from Firm settings, and invitees join automatically the next time they sign in (no separate email step). Everyone in the firm sees the same projects and boards. Each member has a role — owner, admin, or member. You can belong to more than one firm and switch between them from the firm switcher, and billing is handled per firm.
What is the kanban board view?: The board view organizes your issues into columns, with each card showing its linked merge requests and their status. Out of the box, GitLab projects mirror your own board's lists — whether those are labels, statuses, people or milestones — and GitHub projects use Stage:: labels; or you can switch to Your columns and define them yourself. Dragging a card writes the change back to GitLab or GitHub, and what it writes depends on what the column means: a label, an assignee, a milestone, or — on GitLab — a work-item status. GitLab projects require a PAT with api scope for this.
Do board columns have to be labels?: No. A GitLab board is mirrored as it stands: if its lists are statuses, people or milestones rather than labels, those are the columns you get, with nothing to configure. Or switch any board to Your columns and define them yourself — each column can match on a label, a person, a milestone or a GitLab status, so “a column per teammate” or “a column per release” works without inventing labels to stand in for them. Dragging a card into an assignee column reassigns the issue, and into a milestone column sets the milestone, on both GitLab and GitHub.
Does GitGumbo understand GitLab's Status field?: Yes. GitLab 18.4 gave work items a native Status — To do, In progress, Done — intended to replace using labels to track lifecycle. GitGumbo syncs it, shows it on every card, and builds your columns from it: a board whose lists are statuses is mirrored as it stands, so a team that has moved off labels needs to change nothing. Dragging a card between status columns writes the new status back. The field is available on every GitLab tier, not just Premium. This one is GitLab-only: GitHub has no equivalent.
Can I cap how many issues sit in a column?: Yes. Give a column a WIP limit and its header counts against it — 7/5 — turning amber when you reach the limit and red when you go past it. It is a warning, not a wall: GitGumbo never blocks the drag, matching GitLab's own behaviour, because a board that refuses your work just gets worked around. The ratio hides while a filter is active, since a filtered count would be measuring something else.
Does the board show milestones and due dates?: Every card shows its milestone, on both providers. Due dates are GitLab-only — GitHub issues don't have one — and appear as a chip that turns amber within three days of the date and red once it has passed. You can filter the board to a single milestone, or flip on the Overdue toggle to see only what is late.
Is there an API?: Yes — a read-only HTTP API over your projects, issues, merge requests and labels, plus the derived board itself on GitLab: the columns, the issues bucketed into each, and every issue’s linked merge requests in one call. Mint a token at /settings/api — that is your firm’s own API access card, not the provider access tokens on /settings — and send it as a Bearer token. The OpenAPI spec is generated from the same schemas the API serves, so the documentation cannot drift from the behaviour. API access is included on Pro (1,000 requests an hour) and Team (5,000); on Free, requests are refused. See the API reference for every endpoint and schema.
Can I move issues between columns on a phone or tablet?: Yes. On a touch device, dragging a card would fight with swiping the board sideways, so instead each card shows a Move button — an up-and-down arrows icon. Tap it to open a menu of columns and pick where the issue should go; the label updates just as a drag would. The button appears whenever you have permission to move issues (GitLab projects need a PAT with api scope). Everything else — copying the branch name or title, jumping to the MR, toggling draft — works the same on touch as on desktop, with full-size tap targets and no hover.
Can I sort issues within a column?: Yes. Each column has its own sort control. You can sort by idle time, recently updated, oldest first, or MR creation date. Click the same option again to reverse the direction. Your sort choice is remembered across sessions.
What are 'In Review' automations?: In Review automations are per-project actions that fire when you drag an issue into an In Review column. GitGumbo can automatically mark draft merge requests as ready, assign team members to the issue, and add reviewers to the linked MRs. You can configure these in the Settings page for each project.
Can I connect multiple accounts?: Yes. In addition to signing in with OAuth, you can add personal access tokens (PATs) in Settings to connect extra accounts for the same provider. This is useful if you work across multiple GitLab instances or GitHub organizations. Each token is encrypted at rest.
How much does GitGumbo cost?: GitGumbo has a Free plan (3 seats, 1 connected account, up to 5 public repos, 15-minute sync, closed cards kept with no time limit, and no analytics dashboard) and a Pro plan at $9 per seat / month or $90 per seat / year (17% less), for up to 5 seats — unlimited repos, both providers, private repos, real-time sync, the read API, and 90 days of analytics history. A Team tier ($16 per seat / month, no seat limit, 180 days of analytics history, plus the cross-project Insights view) is defined but not yet purchasable — you can join the waitlist from the pricing page. Pro starts with a 14-day free trial, no card required — if you don’t add one, the trial simply ends and you go back to Free. Tax may be added at checkout, depending on your location. See Pricing for the full comparison.