I genuinely cannot understand the thinking here. You took a custom color (the whole point being that we chose it deliberately) and silently overrode it for "contrast," with no toggle to opt out. For teams who use status colors as a functional system, not decoration, this breaks a visual language we built on purpose. Yellow is now mud.

What makes it worse: this wasn't in any release note. I found out because my workspace changed under me, then confirmed it by finding other customers reporting the same thing in this very portal. That's not how you ship a change that alters existing customer configurations.

This is a pattern, not a one-off. Functional changes keep landing with no documentation, and every week something we relied on quietly degrades. At minimum: give us a toggle to keep our exact custom colors, and put functional/visual changes in the release notes so we aren't reverse-engineering what you did to our own workspace.

I've had to change so many colors because this "update" has caused the light colors to darken to the next level. So now everything has to be darkened to keep the easy recognition that had been working perfectly for years.

Hi Maya. Thank you for reporting - we are working on a fix!