Rethinking the CSV export
It shipped behind a flag first, so a handful of workspaces have been on it for a fortnight. Nothing about billing changes, on any plan. Before you start. It is slower on the first…
It shipped behind a flag first, so a handful of workspaces have been on it for a fortnight. Nothing about billing changes, on any plan.
Before you start
It is slower on the first load and faster on every one after. Large workspaces should see the biggest difference, since the old query grew with the number of items. The old behaviour is still reachable for a release, behind a setting.
How it works
Most teams will notice this first on the busiest screen they use. The docs page for this was rewritten alongside it.
What changes
The change is backwards compatible, so integrations built against the old shape carry on unchanged. The limit is generous enough that most teams will never meet it. Thanks to everyone who filed a report with steps; several of them pointed straight at the cause.
- Enable changelog email previews.
- Enable a public API rate-limit dashboard.
Next steps
The API returns the same fields it always has, with one addition. This has been the most requested change on the board for a while, and it is now live for every workspace.
curl -sS https://api.example.test/v2/changelog \
-H "Authorization: Bearer $BULLETIN_API_KEY"
- performance
- api
- breaking