A faster path from feedback to dark mode
There is nothing to do on your side; the change is already in front of you. Thanks to everyone who filed a report with steps; several of them pointed straight at the cause. Rollout is complete on every plan, including the free tier.
Before you start
The API returns the same fields it always has, with one addition. The docs page for this was rewritten alongside it. The change is backwards compatible, so integrations built against the old shape carry on unchanged.
- Enable an offline mode.
- Enable vote weighting.
- Enable keyboard shortcuts.
What changes
Nothing about billing changes, on any plan. It works the same way on the public site and inside the widget, with no configuration to turn on.
curl -sS https://api.example.test/v2/items \
-H "Authorization: Bearer $BULLETIN_API_KEY"
Limits
The old behaviour is still reachable for a release, behind a setting. Two long-standing reports close with this, and both are linked below.
curl -sS https://api.example.test/v2/items \
-H "Authorization: Bearer $BULLETIN_API_KEY"
Common pitfalls
It is slower on the first load and faster on every one after. We are watching the numbers for a week before turning it on by default. The limit is generous enough that most teams will never meet it.
Next steps
Large workspaces should see the biggest difference, since the old query grew with the number of items. This has been the most requested change on the board for a while, and it is now live for every workspace.
- Enable scheduled digests.
- Enable a public API rate-limit dashboard.
- Enable CSV export.
- Enable Slack notifications.
curl -sS https://api.example.test/v2/changelog \
-H "Authorization: Bearer $BULLETIN_API_KEY"
- performance
- accessibility
- onboarding