nextcloud / nextcloud/calendar
free busy sheduling wrongly handles timezone
Open
Nobody has claimed this yet.
1. to develop
bug
Feature: Scheduling
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
- Under "Calendar settings > General" select a timezone different from your browser/OS
- e.g. browser/OS has "Berlin" and "Tokyo" in settings
- Start creating an event
- Add an attendee
- Use "Find a time"
Expected behavior
Time of "Selected slot" (11AM - 1PM in the screenshot) matches with the time of the event (4AM - 6AM).
Actual behavior
Calendar app version
6.5.2
CalDAV-clients used
No response
Browser
No response
Client operating system
No response
Server operating system
No response
Web server
None
Database engine version
None
PHP engine version
None
Nextcloud version
No response
Updated from an older installed version or fresh install
None
List of activated apps
Nextcloud configuration
Web server error log
Log file
Browser log
Additional info
Similar issue as in #8653
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Calendar settings > General timezone flow and the event creation "Find a time" entry point. Reproduce the Berlin/Tokyo mismatch, then trace how the selected slot and event times are displayed; done means both show the same time for a timezone different from the browser or OS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100