nextcloud / nextcloud/server

[Bug]: Merged fix for #36192 Fails [Fix reminder timezone drift for all-day events #36192}

Open
#39,640 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 26-feedback bug feature: caldav feature: language/translations (l10n/i18n)
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

The merged fix for timezone drift for all day event reminders described in bug #36192 is not working properly in NC26.0.4. See https://github.com/nextcloud/server/pull/36192

At least one other user on the nextcloud forum is describing the same. See https://help.nextcloud.com/t/calendar-timezone-bug-36192/167212

Calendar is still using server time (generally UTC) instead of calendar time zone.

Steps to reproduce
  1. create all day event on calendar
  2. schedule email reminder
  3. save event with reminders
Expected behavior

Reminder should arrive as scheduled in users selected time zone. instead reminder is arriving based on server time zone, which is generally UTC. In other words, if reminder should arrive at 9am New York City time (America/NewYork) the day before an all day event, it arrives at 5am New York City time (America/NewYork), because New York is 4 hours later than UTC.

Installation method

Community Web installer on a VPS or web space

Nextcloud Server version

26

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.1

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Fresh Nextcloud Server install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report
i dont know how to do this
List of activated Apps
not sure how to do this
Nextcloud Signing status
not sure how to do this
Nextcloud Logs
not sure how to do this
Additional info

none

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked fix in pull request #36192, then reproduce the all-day event reminder steps described in this issue. Compare the scheduled and delivered times across a non-UTC calendar timezone; done means reminders arrive at the selected timezone rather than server time.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.