Product

A faster path from feedback to dark mode

IDIdris Kaur1 min read

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.

  1. Enable an offline mode.
  2. Enable vote weighting.
  3. 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.

  1. Enable scheduled digests.
  2. Enable a public API rate-limit dashboard.
  3. Enable CSV export.
  4. Enable Slack notifications.
curl -sS https://api.example.test/v2/changelog \
  -H "Authorization: Bearer $BULLETIN_API_KEY"
  • performance
  • accessibility
  • onboarding
8,724 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
  • Rethinking search

    We are watching the numbers for a week before turning it on by default. It shipped behind a flag first, so a handful of workspaces have been on it for a fortnight. Nothing about b…

    NONoah Moreau1 min read
  • Rethinking the changelog

    Thanks to everyone who filed a report with steps; several of them pointed straight at the cause. It is slower on the first load and faster on every one after. Before you start. An…

    DMDmitri Reyes1 min read