About GitGumbo

What is GitGumbo?

GitGumbo is a kanban board for teams using GitLab and GitHub. It organizes your issues into columns and enriches every card with live merge request data — pipeline status, merge conflicts, unresolved review threads, idle time, labels, and more — so you can see the health of every MR at a glance and jump straight to the ones that need attention.

The problem

GitLab and GitHub show you issues and merge requests, but the details you need — a failing pipeline, a forgotten review thread, an MR that’s been sitting idle for a week — are buried behind clicks. You have to open an issue, find the MR link, open the MR, then check its pipeline and threads. Teams end up context-switching between tabs or relying on memory to keep track of what’s happening.

How GitGumbo helps

• Kanban boards — Your issues organized on a board, with every card showing its linked MRs so you can see the state of a project at a glance and spot bottlenecks immediately. GitLab projects mirror your own board’s lists automatically — labels, statuses, people or milestones, whichever you built it from; GitHub projects use Stage:: labels.
• Columns that aren’t just labels — A GitLab board organized by status, by person or by milestone is mirrored as it stands. Or define your own columns, where each one can match on a label, a person, a milestone or a GitLab status, so organizing by teammate or by release doesn’t mean inventing labels to stand in for them. Dragging a card writes the change back to GitLab or GitHub — reassigning the issue, setting the milestone, or updating the label, depending on what the column means. On GitLab, a column can also be a work-item Status, the field GitLab added to replace tracking lifecycle with labels. Columns can carry a WIP limit too: the header counts against it and colours as you approach and pass it, without ever blocking the drag.
• Rich detail on every MR — Pipeline status, merge conflicts, unresolved review threads, draft state, approval status, and how long an MR has been idle — all visible without leaving GitGumbo.
• Per-column sorting — Sort issues within each board column independently by idle time, recently updated, oldest first, or MR creation date. Click the same option again to reverse the direction.
• Powerful filtering — Filter by assignee, label, milestone, pipeline status, conflicts, draft state, or unresolved threads to zero in on exactly what you care about — or show only what is overdue. Cards carry their milestone, and on GitLab their due date, as a chip that turns amber within three days and red once the date has passed.
• “In Review” automations — When you drag an issue into an In Review column, GitGumbo can automatically mark draft MRs as ready, assign team members to the issue, and add reviewers to the linked MRs. Configure per project in Settings.
• One-click navigation — Every MR links directly back to GitLab or GitHub so you can jump to it the moment you spot something that needs action.
• A read API — Everything the board knows is available over a read-only HTTP API: projects, issues, merge requests, labels, and on GitLab the derived board itself — columns, the issues in each, and every issue’s linked merge requests in a single call. The OpenAPI spec is generated from the same schemas the API serves, so it cannot drift. Included on Pro and Team; see the API reference.
• Real-time sync — on Pro, GitGumbo registers webhooks with GitLab and GitHub (where the connected account has permission to create them), so most changes are reflected within seconds. A background sync always runs automatically as the baseline — and the only mechanism on Free — catching anything webhooks miss. Syncs are incremental by default, so when nothing has changed the overhead is very low, and you can trigger a manual sync from the board at any time.

GitLab & GitHub

GitGumbo works with both GitLab.com and GitHub.com. Sign in with your existing account and add the projects you want to track — that’s it. Self-hosted GitLab and GitHub Enterprise Server aren’t supported yet.

GitLab users will find the board view instantly familiar — it follows the same kanban layout as GitLab’s issue boards, but with MR data on every card. Pipeline status, conflicts, review threads, and idle time are all right there, cutting out the constant clicking between MR pages.

GitHub users get something neither GitHub Issues nor Projects gives you: every issue’s pull requests shown on its card, with full PR detail, filtering, and one-click navigation back to GitHub.

Connecting your account

GitGumbo uses OAuth to connect to your GitLab or GitHub account. You sign in with your existing credentials — GitGumbo never sees or stores your password. You can also connect multiple accounts for the same provider by adding personal access tokens (PATs) in Settings, which is useful for teams that work across several GitLab groups or GitHub organizations.

What gets synced

Once you add a project, GitGumbo pulls in your open issues and their linked merge requests. For each MR it also fetches the pipeline status, CI job results, approval state, review threads, conflict status, and labels. Syncs run automatically in the background, and on Pro GitGumbo registers webhooks so changes in GitLab or GitHub are reflected within seconds. You can also trigger a manual sync from the board at any time. All tokens are encrypted at rest — GitGumbo never accesses your source code or commit contents.

Teams & firms

GitGumbo organizes work into firms — shared workspaces that own boards and members. Everyone in a firm sees the same projects and boards, so your whole team works from one view instead of each person tracking their own copy.

Owners and admins invite teammates by email or username from Firm settings. Invited people join automatically the next time they sign in — there’s no separate email step to chase. Each member has a role: owner, admin (can manage members and firm settings), or member (works the shared boards).

You can belong to more than one firm — say a personal workspace and a shared team firm — and switch between them from the firm switcher in the top bar. Working solo? You get your own private firm by default, with nothing to set up. Billing is handled per firm, so a single subscription covers everyone in it.

Built for teams

Whether you’re a small team with a handful of repos or a larger organization juggling dozens of projects, GitGumbo gives you a single place to see the full state of your merge requests. Less time clicking through tabs means more time shipping code.