KamoCRM

Bucket the history by the member's day, not the browser's

Fixkamo-internal
Shipped
22 ஆகஸ்ட், 2026 அன்று 11:42 AM UTC
Author
kamo
Commit
8d5bc81

groupByDay built its day key from getFullYear/getMonth/getDate, which read the machine's calendar rather than the member's. With createdAt now parsed as the UTC it always was, that showed up as a real disagreement: a 5pm Pacific notification filed under tomorrow for a member whose laptop is set to UTC, and two days collapsing into one when the suite ran in Tokyo. Both entry points take the member's zone and go through zonedDayKey, and the group is dated at the start of that day rather than at local midnight. The tests name the zone instead of inheriting the machine's — the suite now passes in Los Angeles, Tokyo and Kolkata alike, which is the property that was missing.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing