Skip to content

fix: calendar reminder timezone handling#210

Closed
realmpastai-web wants to merge 145 commits intoTeamNovaSoft:mainfrom
realmpastai-web:fix/calendar-timezone-reminder
Closed

fix: calendar reminder timezone handling#210
realmpastai-web wants to merge 145 commits intoTeamNovaSoft:mainfrom
realmpastai-web:fix/calendar-timezone-reminder

Conversation

@realmpastai-web
Copy link

@realmpastai-web realmpastai-web commented Mar 1, 2026

Closing to retarget dev branch

joset98 and others added 30 commits March 6, 2025 16:10
heliomar-pena and others added 27 commits April 1, 2025 09:48
…ate-doc-to-github-webhook

Doc/iss 183/create doc to GitHub webhook
…e-user-selector

refactor: improve command flow with user selector
…nedTagId

fix: log ASSIGN_TASK_FORUM env to check values
…stack-assign-task-command

fix: add error stack in object to show in assign task command
…v-proposal-for-point-registration

feat: add proposal
…eminder-is-not-timezone-rebase

Feat/calendar reminder is not timezone rebase
…-section

fix: add default section to show simple descriptions
…l-votation-MessageUpdate

Feat/iss 30/poll votation message update
Fixes TeamNovaSoft#109

The issue was that cron expressions were generated using the server's
local timezone (getHours/getMinutes), but the CronJob was scheduled
with the event's timezone. This caused a mismatch when events were
in different timezones than the server.

Changes:
- Added dateToCronExpressionInTimezone() helper function that uses
  Intl.DateTimeFormat to extract date components in the event's timezone
- Updated scheduleEventNotification() to use the timezone-aware function
- Added comprehensive tests for timezone handling

Before: Event at 1pm Argentina scheduled reminder for 1pm Colombia (2h late)
After: Event at 1pm Argentina correctly schedules reminder for 1pm Argentina
@realmpastai-web
Copy link
Author

/claim #109

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants