Meetings, incidents with an on-call rota, public status pages, a feedback board with voting, sprints, goals, releases, fifteen new board types, invoicing, a GitHub App, 80 MCP tools and 51 webhook events. Here is the short version.
2026-10-12
We had a quiet week planned. Then somebody opened the backlog, and 288 commits later devbord does roughly twice what it did on Thursday. This is the tour. It is long, because the list is long, and we are not sorry.
A project used to be a kanban board with a few alternative views. It now holds whatever your team keeps in six other tabs:
- **Planning**: sprint (backlog, burndown, past sprints), roadmap, goals with key results, a matrix with two axes you pick yourself, a dependency graph of what blocks what, and a gallery.- **Shipping**: releases (cards carry their release, and a matching deploy marks it shipped), test runs with a release gate, and a changelog with an editor, a public page and announcements.- **Talking**: an async stand-up board with reminders, a chat summary and blocker cards, retrospectives, and a decision log for the next time someone asks why it was built that way.- **Listening**: a feedback board with public voting and a public roadmap next to it.- **Firefighting**: incidents and on call. Those get their own section.
Boards and whole projects take their sprints, goals and changelog versions along when you copy, export or import them.
Meetings have an agenda, shared notes, action items and carry-over: what was not finished shows up on the next one, whether you like it or not.
On top of that: timeboxes per agenda item, a live mode, decisions, attendance, RSVP, a parking lot for the topic that would otherwise eat the hour, reminders for open action items and an email summary after closing. Two people writing notes at the same moment get merged instead of overwritten. There is a calendar feed, and a Discord bot with reminders, a summary and a `/meeting` command.
The incidents board gives every incident a timeline, a postmortem and follow-up cards. New incidents go to whoever is on call, according to a rota with covers and its own time zone. They have to acknowledge it. If they do not, it escalates. At shift change, the person taking over is told which incidents are still running, so "I thought you had it" is off the table.
Incident pushes arrive as time-sensitive on iOS, so they can get through a Focus that allows those. Sleeping through it now takes effort.
Public status pages are new as well: uptime history, incidents, an RSS feed, email subscribers, a custom domain and ten languages, fixed per page or following the visitor. Incidents can be reported on the page automatically, and a page can post its updates to a Discord channel through a plain webhook, no bot required.
- Connect GitHub through a GitHub App, or link GitLab and Forgejo/Gitea repositories to a board the same way.- Cards show their branches and pull requests with review state, CI and commits.- Deploy tracking: a deploy hook per project, deploys from GitHub and GitLab, and a rule trigger for cards that shipped.- Automation reacts to branches, commits, pull requests and CI, including "approved" and "changes requested". It can also send and receive plain web requests, post to Slack and Teams, send email, start timers and assign people in turn.
Also new: email to card, with an address per board, and a calendar subscription for your cards and for a project's calendar.
- An Explore view with breakdowns over time and release markers, alert rules with a users-affected trigger, a review state, ignore-until conditions and an activity timeline with comments.- Apdex in performance, release-over-release deltas, CSV export, CODEOWNERS import, browser CSP reports as issues, and erasing the data of one end user when they ask.- `@devbord/browser` and `@devbord/node` are on npm: thin layers over the Sentry SDK, so moving over is a change of the import.- Bug reports from inside a game or app: a report intake API with intake-only keys, deduplication and receipts, plus ready-made integrations for Minecraft, Roblox, Unity and FiveM. On Discord, `/bugreport` files one and tells the reporter when it is fixed.
The time page was rebuilt with team timesheets and invoicing from billable hours. Invoices come as PDF, can be emailed, chased with reminders, credited, and exported as UBL e-invoices. Around that: money budgets, fixed fees and a forecast per project, cost rates with margin, time estimates on cards, idle detection for the timer you forgot, bulk editing, scheduled report emails and public share links for saved reports.
Last time the MCP server had 22 tools. It has 80 now: goals, sprints, meetings, documents, time tracking, retrospectives, incidents, on-call shifts and the weekly overview are all in there, and in the REST API.
Webhooks cover 51 events, including incidents, on call, sprints, releases, retros and documents. There is a test button, and the API docs show an example payload for every event, so you can write the handler before the event ever happens.
- A glass look across the app, a Start page you build from widgets, a rebuilt My cards, a notifications page, and chat with grouped messages, day separators and typing indicators.- Boards update in place when someone else changes them: only the affected cards move, and your scroll position stays where you left it. Rendering and app boot got faster, and scrolling is smooth in Firefox and Zen.- Per-feature permissions for roles, and tracked time and rates that stay private unless a role says otherwise.- A weekly overview per project, by email if you want it, with an opt-out per member if you do not.- The public site, pricing page and API docs were rebuilt.
The app caught up with nearly all of it: every board type above, meetings, incidents with time to acknowledge, releases and retros, error tracking with push, the rule editor, time tracking with a Live Activity, a home screen widget, a share extension that makes cards, and a proper iPad layout with a sidebar, cards beside the board and keyboard shortcuts.
- Extra kanban boards are part of every plan. The other board types are Premium.- The API, the MCP server and webhooks are Premium, as are error tracking and time tracking.- Report-only keys also work on Standard, with 50 reports a month.
The reference for everything with an endpoint is in the [API documentation](/api-docs). Everything else is one click on "new board" away.
devbord · Plans · News · API documentation · What we can and cannot see
devbord requires JavaScript to work.