Upcoming cards logic seems to rely on UTC time instead of adjusting for timezone
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Describe the bug
It's currently just past 10am EST, the card is due at 8pm today (relative time was calculated correctly), however, the card is shown as scheduled for tomorrow. Furthermore, in Tasks, the same card is reporting as due for it's UTC equivalent (Tomorrow 1am).
Client timezone: EST
VM timezone: UTC/EST (same behaviour with either)
Environmental variable: EST
To Reproduce
Steps to reproduce the behavior:
- Change timezone to something other than UTC
- Create a card that is due today in local time but tomorrow in UTC
- Open "Upcoming cards" page
- The card is listed as due tomorrow
Expected behavior
The card is listed as due today
Screenshots
Client details:
- OS: Windows 10
- Browser: Chrome
- Version: Deck 1.11.3
- Device: Desktop PC
Server details
Operating system: Ubuntu Server 22.04 LTS (Using the official Docker images)
Web server: Nextcloud Apache
Database: PostgreSQL 15.5 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
PHP version: 8.1.25
Nextcloud version: 27.1.4
Where did you install Nextcloud from: Docker Hub
Signing status:
List of activated apps:
Nextcloud configuration:
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Logs
Nextcloud log (data/nextcloud.log)
Browser log
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 at the Upcoming cards page and reproduce the issue with a non-UTC client timezone, using a card due today locally but tomorrow in UTC. The fix is complete when the card is listed as due today, matching the local time shown in Tasks.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100