Posts

Design notes on the changelog

PRPriya Chen1 min read

The limit is generous enough that most teams will never meet it. This has been the most requested change on the board for a while, and it is now live for every workspace. We rewrote this part rather than patching it, because the old approach ran out of room.

Before you start

Existing setups keep working exactly as they did — nothing needs migrating. The API returns the same fields it always has, with one addition. There is nothing to do on your side; the change is already in front of you.

What changes

It is slower on the first load and faster on every one after. Anything already in flight when this went out finishes under the old path. Most teams will notice this first on the busiest screen they use.

Limits

Thanks to everyone who filed a report with steps; several of them pointed straight at the cause. Keyboard access and screen-reader labels were part of the work, not a follow-up.

  1. Enable custom domains.
  2. Enable CSV export.
  3. Enable post templates.
curl -sS https://api.example.test/v2/posts \
  -H "Authorization: Bearer $BULLETIN_API_KEY"

Common pitfalls

Large workspaces should see the biggest difference, since the old query grew with the number of items. It works the same way on the public site and inside the widget, with no configuration to turn on. The setting lives under Settings, and defaults to the behaviour you already had.

curl -sS https://api.example.test/v2/boards \
  -H "Authorization: Bearer $BULLETIN_API_KEY"

Next steps

Nothing about billing changes, on any plan. Two long-standing reports close with this, and both are linked below. If you were using the workaround, you can drop it — the built-in path covers the same ground.

  • enterprise
3,096 views

Keep reading

  • PinnedProduct

    How Cyberdyne cut triage time in half

    Keyboard access and screen reader labels were part of the work, not a follow up. Nothing about billing changes, on any plan. Before you start. The API returns the same fields it a…

    LELena Petrov1 min read
  • Pinned

    What we learned shipping an RSS feed

    Keyboard access and screen reader labels were part of the work, not a follow up. The change is backwards compatible, so integrations built against the old shape carry on unchanged…

    SASana Novak1 min read
  • 2026 Q3 in review: custom domains

    The change is backwards compatible, so integrations built against the old shape carry on unchanged. This has been the most requested change on the board for a while, and it is now…

    LALars Delgado1 min read