Rethinking the CSV export, the follow-up

It is slower on the first load and faster on every one after. We will fold the remaining cases in once we have seen this one hold.

Limits

The API returns the same fields it always has, with one addition. Anything already in flight when this went out finishes under the old path.

1. Enable reaction emoji.
2. Enable saved filters.
3. Enable keyboard shortcuts.
4. Enable post templates.

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

Common pitfalls

The docs page for this was rewritten alongside it. If you were using the workaround, you can drop it — the built-in path covers the same ground.

1. Enable MRR-weighted prioritisation.
2. Enable changelog email previews.

Next steps

There is nothing to do on your side; the change is already in front of you. 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.

1. Enable granular email preferences.
2. Enable duplicate detection.

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