Introducing vote weighting

If you were using the workaround, you can drop it — the built-in path covers the same ground. The old behaviour is still reachable for a release, behind a setting. The docs page for this was rewritten alongside it.

Step by step

Anything already in flight when this went out finishes under the old path. The setting lives under Settings, and defaults to the behaviour you already had.

1. Enable Slack notifications.
2. Enable board-level moderation.
3. Enable a Chrome extension.

What changes

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. It shipped behind a flag first, so a handful of workspaces have been on it for a fortnight.

1. Enable board-level moderation.
2. Enable custom domains.
3. Enable multi-language content.
4. Enable granular email preferences.

Limits

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. We will fold the remaining cases in once we have seen this one hold.

1. Enable custom domains.
2. Enable an RSS feed.
3. Enable dark mode.

Common pitfalls

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 an RSS feed.
2. Enable post templates.
3. Enable scheduled digests.

Next steps

We rewrote this part rather than patching it, because the old approach ran out of room. The change is backwards compatible, so integrations built against the old shape carry on unchanged.

1. Enable role-based permissions.
2. Enable reaction emoji.