stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Make Week Ahead calendar import timezone-correct and range-bounded #1212

New Issue
Closed
opened 2026-08-21 06:27:43 +00:00 by timmy · 0 comments
timmy commented 2026-08-21 06:27:43 +00:00
Owner
Copy Link

Problem

Private Week Ahead calendar import discards ICS TZID parameters, so a 12:00 America/New_York event is treated as 12:00 in every browser timezone. Recurrence expansion also walks from the historical series origin before clipping to the seven review dates, allowing old calendars to freeze mobile devices.

User outcome

Import Google/Outlook calendars with IANA time zones and receive correct local capacity and conflict-free export. Long-running daily/weekly series perform work bounded to the seven-day review range. Unknown zones fail closed without exposing event metadata.

Acceptance tests

  • A 12:00 America/New_York event occupies 09:00 on an America/Los_Angeles device.
  • Daily recurrence retains declared wall time across DST.
  • Unknown TZID disables Apply with count-only diagnostics.
  • Historical daily/weekly series are fast-forwarded to the review window while preserving COUNT/UNTIL/EXDATE/RDATE semantics.
  • Existing floating/UTC behavior and packaged mobile calendar journey remain green.

No historical issue title or recent commit covers ICS TZID parsing or bounded recurrence expansion.

## Problem Private Week Ahead calendar import discards ICS `TZID` parameters, so a 12:00 America/New_York event is treated as 12:00 in every browser timezone. Recurrence expansion also walks from the historical series origin before clipping to the seven review dates, allowing old calendars to freeze mobile devices. ## User outcome Import Google/Outlook calendars with IANA time zones and receive correct local capacity and conflict-free export. Long-running daily/weekly series perform work bounded to the seven-day review range. Unknown zones fail closed without exposing event metadata. ## Acceptance tests - A 12:00 America/New_York event occupies 09:00 on an America/Los_Angeles device. - Daily recurrence retains declared wall time across DST. - Unknown TZID disables Apply with count-only diagnostics. - Historical daily/weekly series are fast-forwarded to the review window while preserving COUNT/UNTIL/EXDATE/RDATE semantics. - Existing floating/UTC behavior and packaged mobile calendar journey remain green. No historical issue title or recent commit covers ICS TZID parsing or bounded recurrence expansion.
timmy self-assigned this 2026-08-21 06:27:43 +00:00
timmy closed this issue 2026-08-21 06:57:17 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#1212
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?