Three questions board filters should answer

It shipped behind a flag first, so a handful of workspaces have been on it for a fortnight. Keyboard access and screen-reader labels were part of the work, not a follow-up.

How it works

The limit is generous enough that most teams will never meet it. We rewrote this part rather than patching it, because the old approach ran out of room.

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

Step by step

If you were using the workaround, you can drop it — the built-in path covers the same ground. Large workspaces should see the biggest difference, since the old query grew with the number of items. 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"

What changes

Thanks to everyone who filed a report with steps; several of them pointed straight at the cause. The old behaviour is still reachable for a release, behind a setting.

Common pitfalls

We are watching the numbers for a week before turning it on by default. The docs page for this was rewritten alongside it.

Next steps

We will fold the remaining cases in once we have seen this one hold. This has been the most requested change on the board for a while, and it is now live for every workspace. Anything already in flight when this went out finishes under the old path.

1. Enable SAML SSO.
2. Enable Zapier triggers.