Behind the scenes: our move to dark mode
Nothing about billing changes, on any plan. Anything already in flight when this went out finishes under the old path. Before you start. We rewrote this part rather than patching…
Nothing about billing changes, on any plan. Anything already in flight when this went out finishes under the old path.
Before you start
We rewrote this part rather than patching it, because the old approach ran out of room. We are watching the numbers for a week before turning it on by default. The change is backwards compatible, so integrations built against the old shape carry on unchanged.
Step by step
It works the same way on the public site and inside the widget, with no configuration to turn on. Keyboard access and screen-reader labels were part of the work, not a follow-up. Most teams will notice this first on the busiest screen they use.
What changes
Thanks to everyone who filed a report with steps; several of them pointed straight at the cause. It shipped behind a flag first, so a handful of workspaces have been on it for a fortnight.
Limits
The setting lives under Settings, and defaults to the behaviour you already had. Large workspaces should see the biggest difference, since the old query grew with the number of items.
- Enable internal notes.
- Enable board-level moderation.
Common pitfalls
It is slower on the first load and faster on every one after. Two long-standing reports close with this, and both are linked below. If you were using the workaround, you can drop it — the built-in path covers the same ground.
- accessibility
- search