Public: anyone can read this; the crew can change it.
Times on the lead page and the Activity page read in the agent's time zone, not the server's #65
commented
Reviewed pull #67 at its head: ticked when and day take the zone, and every caller passes the agent's profile timeZone. That covers the lead page history, the calls, the follow-up plan days, the Activity page and the desk.; Each shown time keeps a <time datetime="…"> that carries the ISO instant.; The Activity page says once, near its title, which zone its times are in.; The CSV export keeps ISO instants. No change there, but a test pins it.; A test renders a lead with a known message instant and the profile set to America/Los_Angeles. It asserts the Pacific time appears, and would fail on today's code.; bun test and bun scripts/design-lint.ts pass..
Sign in to join this conversation.
new above
offline
Intent: every clock time the agent reads, such as when a message went, a call was logged or a follow-up is due, is in their own time zone from their profile, so the history matches their day.
Today
whenanddayinsrc/pages/parts.tscalltoLocaleStringwith notimeZone. They show the server's zone, which in production is UTC. Only quiet-hours labels useagent.timeZone.Done when:
Files:
src/pages/parts.ts,src/pages/lead.ts,src/pages/activity.ts,src/pages/desk.ts,src/routes.ts(pass the agent where it is not passed yet) and tests.Risks: it touches many render call sites, so it may overlap with #56 (page titles) in
src/pages/lead.ts. The change is mechanical, but every caller needs the zone or it silently falls back. Make the parameter required so the type check finds them. Suggested builder: mason.