Boards that follow your GitHub Project's Status
A GitHub board can now follow a GitHub Project. Its columns are the Project's Status options, cards sit where the Project puts them, and dragging a card changes its Status in GitHub.
A GitHub board can now follow a GitHub Project. Its columns are the Project's Status options, cards sit where the Project puts them, and dragging a card changes its Status in GitHub.
When a pipeline has been unfinished for three hours or more, its card shows a clock and the tooltip says how long it has been going and which jobs are holding it up.
The Free plan now takes private repositories as well as public ones, so you can try GitGumbo on the work your team actually does.
Server logs no longer carry issue titles, names, email addresses or repository paths, and the web server's request log now lives in memory instead of on disk.
Owners and admins of a firm on a trial now see a banner in its last three days, on top of the reminder email a week before.
When a linked card is scrolled out of its column, the line now stops at that column's edge and points straight up or down, and a click on its label brings the card into view.
The database, the cache, the backups and our own secrets have moved onto an encrypted disk that unlocks only by reaching a key server kept elsewhere. Titles and tokens stay encrypted a second time inside it.
GitHub pull requests into a non-default branch now link to the issues they close, GitLab MRs can close an issue by its URL, keywords inside code no longer count, and a linked issue in another project is named when you can read it.
Cards now show GitLab and GitHub "relates to" links in a quiet chip of their own, with dashed lines to the related cards, a Related filter, and a setting to hide them.
The board's search box now finds cards by issue number, and by the number of a linked merge request or pull request.
The linked-issues panel now says which column each linked card is in, and one Blocked/Blocking filter shows both ends of a dependency together.
Start a pull request for a GitHub issue without leaving the board. It creates a branch and a draft pull request that closes the issue when it merges.
The support page can now answer questions about GitGumbo in plain words, from the guides, at any hour.
Thirteen help guides at /docs, a search that finds the right section, and a support page where you can send us a message.
The Sync menu now says what each choice does, GitLab cards in a Status column can be closed from the board, and Insights saved filters can be named, renamed and managed in place.
Leave a firm yourself, sign out of every device at once, export everything you hold across your firms, and clearer messages when a sign-in can't go ahead.
The billing page now says when a trial ends, repositories paused by Free's limit start syncing again when you upgrade, and deleting a paid team refunds the unused time.
Drop a card on Closed, or pick Closed in the move menu, and the issue is closed. On GitLab, dragging it back out reopens it.
A GitLab project's board now mirrors your GitLab issue board list for list, labels, statuses, people and milestones, and moving a card does what it would do on GitLab.
GitLab tasks, incidents and test cases now carry a type chip on their card, and the filter bar can show just one type.
Column automations used to fire on a column picked by its name. You now choose the column yourself, GitLab Status columns included, and the board's nudge takes you straight to the right setting.
It started as a command-line script that found merge requests nobody had looked at in a while. It is now the screen we keep open all day instead of GitLab's own boards.
We ran a full audit, fixed what it found, and shipped three accessibility settings. Here is what is genuinely fixed, what is now opt-in, and what still is not good enough.
A board used to render everything the syncing account could see, for everyone in the firm. Visibility is now resolved per viewer, against that viewer's own provider account.
Start a merge request for a GitLab issue without leaving the board. It creates a draft, with a branch, linked back to the issue.
Day-first, month-first, or ISO. One pinned format for everybody was a decision nobody made deliberately.
Issue titles are the most identifying thing we hold. They are now encrypted in the database and in the nightly backup, and the plaintext columns are gone rather than merely unused.
GitHub's issue dependencies now light up the same blocked and blocking indicators that GitLab boards have.
Issue link relationships now render on the board — both directions — with lines drawn between the cards involved. Confidential GitLab issues are also marked as confidential.
Cards that look like index cards on a desk, and cards that look like sticky notes. A physical-looking board for people who miss the wall.
Downgrading is now a control on the billing page, next to the one that upgraded you. Leaving should be as easy as arriving.
Drag a card up or down inside its own column to set its position, on GitLab boards — with a keyboard and switch-accessible path that does the same thing.
Columns can carry a WIP limit and show when they are over it — and a column that cannot have one now explains why rather than leaving a blank space.
GitLab boards can build lists from assignees or milestones rather than labels. Those boards now render, and a board with lists we cannot draw says so instead of quietly dropping them.
Cards now show the milestone they belong to and the date they are due, on both providers, and both are exposed on the public API.
A density toggle that shrinks cards vertically, so you can see substantially more of a busy board without scrolling.
The theme set is now Light, Dark, High Contrast, Gruvbox and Dracula — plus System, which follows your operating system instead of making you choose.
A statistics view over your board's history — throughput, cycle time, work in progress, age distribution, contributors and review activity.
A project with several GitLab boards no longer collapses into one. Pick which board you are looking at from the board itself.
There are two clocks between a change in GitLab and a change on your screen, they run at different speeds, and they are measured in different units. Here is what each one does.
The theme you pick is now stored against your account rather than in one browser, so it is the same on your laptop, your desktop and your phone.
Projects, boards and billing now belong to a firm rather than to one person, so a team can share a board and a subscription without sharing a login.
GitGumbo now has paid plans, with Stripe checkout, a self-serve billing portal, and project limits that follow your plan.
GitLab and GitHub can now tell us when something changes instead of waiting to be asked, and GitLab webhook registration is scope-aware so it fails loudly rather than silently.
Issues now render as cards in columns, and the columns come from the labels your project already uses rather than from a workflow you have to describe to us again.