github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-30 13:46:39 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

CalDAV: Times have offset of timezone #1790

New Issue
Closed
opened 2026-03-22 13:37:46 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-03-22 13:37:46 -05:00
Owner
Copy Link

Originally created by @mtettke123 on GitHub (Jul 14, 2022).

There seems to be a small bug when syncing times via CalDAV:
Date/Time in App (Tasks.org)
index

Date/Time Synced to Vikunja:
grafik

Timezone:
grafik

The offset seems to be exactly the timezone...

Originally created by @mtettke123 on GitHub (Jul 14, 2022). There seems to be a small bug when syncing times via CalDAV: Date/Time in App (Tasks.org) ![index](https://user-images.githubusercontent.com/82048170/178934463-c7317922-e338-41c5-84c7-0da147690835.jpg) Date/Time Synced to Vikunja: ![grafik](https://user-images.githubusercontent.com/82048170/178934604-ea78659e-fe2b-44ca-87c1-90583b6c6671.png) Timezone: ![grafik](https://user-images.githubusercontent.com/82048170/178934691-af5ee58c-dd58-4724-9a7d-4c75962563a7.png) The offset seems to be exactly the timezone...
GiteaMirror added the bug label 2026-03-22 13:37:46 -05:00
GiteaMirror commented 2026-03-22 13:37:47 -05:00
Author
Owner
Copy Link

@theryxs commented on GitHub (Jul 18, 2022):

Vikunja uses 'GMT' as default timezone if none is configured.
https://vikunja.io/docs/config-options/#timezone

Setting the environment variable to CET for Europe/Berlin worked for me.

@theryxs commented on GitHub (Jul 18, 2022): Vikunja uses 'GMT' as default timezone if none is configured. https://vikunja.io/docs/config-options/#timezone Setting the environment variable to CET for Europe/Berlin worked for me.
GiteaMirror commented 2026-03-22 13:37:48 -05:00
Author
Owner
Copy Link

@mtettke123 commented on GitHub (Jul 19, 2022):

Doesn't work for me. Changed
VIKUNJA_SERVICE_TIMEZONE: "Europe/Berlin"
to
VIKUNJA_SERVICE_TIMEZONE: "CET"

  • no changes.

Even tried without VIKUNJA_SERVICE_TIMEZONE being set - same result.

@mtettke123 commented on GitHub (Jul 19, 2022): Doesn't work for me. Changed VIKUNJA_SERVICE_TIMEZONE: "Europe/Berlin" to VIKUNJA_SERVICE_TIMEZONE: "CET" - no changes. Even tried without VIKUNJA_SERVICE_TIMEZONE being set - same result.
GiteaMirror commented 2026-03-22 13:37:49 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 2, 2022):

Vikunja returns all time zones in utc. It should be the responsibility of the client to adjust it based on the time configured on the client.

The time zone in VIkunja's settings is only used to handle reminders and other transactional emails.

@kolaente commented on GitHub (Aug 2, 2022): Vikunja returns all time zones in utc. It should be the responsibility of the client to adjust it based on the time configured on the client. The time zone in VIkunja's settings is only used to handle reminders and other transactional emails.
GiteaMirror commented 2026-03-22 13:37:50 -05:00
Author
Owner
Copy Link

@mtettke123 commented on GitHub (Aug 2, 2022):

Is the Timezone setting in Vikunja used by the Frontend to adjust the time? It's so strange: If I send a due date via CalDAV it's off by 2 hours in Vikunja web regardlessly if the timezone ist set... And it doesn't seem to matter if I change the setting in the docker-compose file or in the vikunja web interface in settings...

@mtettke123 commented on GitHub (Aug 2, 2022): Is the Timezone setting in Vikunja used by the Frontend to adjust the time? It's so strange: If I send a due date via CalDAV it's off by 2 hours in Vikunja web regardlessly if the timezone ist set... And it doesn't seem to matter if I change the setting in the docker-compose file or in the vikunja web interface in settings...
GiteaMirror commented 2026-03-22 13:37:51 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 2, 2022):

Is the Timezone setting in Vikunja used by the Frontend to adjust the time?

It's not. That depends on your browser.

@kolaente commented on GitHub (Aug 2, 2022): > Is the Timezone setting in Vikunja used by the Frontend to adjust the time? It's not. That depends on your browser.
GiteaMirror commented 2026-03-22 13:37:54 -05:00
Author
Owner
Copy Link

@bfly75 commented on GitHub (Dec 4, 2022):

Vikunja returns all time zones in utc. It should be the responsibility of the client to adjust it based on the time configured on the client.

the date-times in the VTODO object obtained from Vikunja's CalDav seems to 'floating' and not bound to any time zone in particular:
DUE:20221209T144501

If it has to be truely a fixed UTC time, it should end with 'Z' :

DUE:20221209T144501Z

At least the Open-Xchange Caldav server also includes the 'Z'.

See also: https://icalendar.org/iCalendar-RFC-5545/3-3-5-date-time.html

@bfly75 commented on GitHub (Dec 4, 2022): > Vikunja returns all time zones in utc. It should be the responsibility of the client to adjust it based on the time configured on the client. the date-times in the VTODO object obtained from Vikunja's CalDav seems to 'floating' and not bound to any time zone in particular: DUE:20221209T144501 If it has to be truely a fixed UTC time, it should end with 'Z' : DUE:20221209T144501Z At least the Open-Xchange Caldav server also includes the 'Z'. See also: https://icalendar.org/iCalendar-RFC-5545/3-3-5-date-time.html
GiteaMirror commented 2026-03-22 13:37:55 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 4, 2022):

Changing VIkunja's calDAV output so that it always adds the Z suffix to dates is easy, but that does not solve the original problem. Task.org seems to send dates without any time zone attached to them and thus they are assumed to be UTC and saved as such in the db. When opening the task in the browser, it converts the returned utc date to the time zone set in the browser.

@kolaente commented on GitHub (Dec 4, 2022): Changing VIkunja's calDAV output so that it always adds the `Z` suffix to dates is easy, but that does not solve the original problem. Task.org seems to send dates without any time zone attached to them and thus they are assumed to be UTC and saved as such in the db. When opening the task in the browser, it converts the returned utc date to the time zone set in the browser.
GiteaMirror commented 2026-03-22 13:37:57 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 4, 2022):

I've added the Z suffix in c3de15aa892f273ecdc5fb353d65b076c04b95a3. Given the rest seems to be a client limitation, I'll close this issue now.

Don't hesitate to ping if you encounter other problems.

@kolaente commented on GitHub (Dec 4, 2022): I've added the `Z` suffix in c3de15aa892f273ecdc5fb353d65b076c04b95a3. Given the rest seems to be a client limitation, I'll close this issue now. Don't hesitate to ping if you encounter other problems.
GiteaMirror commented 2026-03-22 13:37:58 -05:00
Author
Owner
Copy Link

@andersmmg commented on GitHub (Dec 6, 2022):

This seems to fix the issue for me as well, with Vikunja configured to use my time zone and Tasks.org shows it the same!

@andersmmg commented on GitHub (Dec 6, 2022): This seems to fix the issue for me as well, with Vikunja configured to use my time zone and Tasks.org shows it the same!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#1790
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?