caldav doesn't correctly report timezone #844

Closed
opened 2021-04-22 00:08:15 +00:00 by tunacatmeow · 2 comments

[caldav]

When importing tasks with davx5, all task due times are incorrect by my timezone's offset from GMT. Looking at the ouptut of the caldav, it doesn't indicate what timezone the dates are in, and I believe that davx5 is assuming they are in GMT.

[caldav] When importing tasks with davx5, all task due times are incorrect by my timezone's offset from GMT. Looking at the ouptut of the caldav, it doesn't indicate what timezone the dates are in, and I believe that davx5 is assuming they are in GMT.
Owner

Did you configure any time zone?

Did you configure any time zone?
konrad added the
kind/bug
label 2021-05-26 06:49:59 +00:00
Owner

I'm closing this due to inactivity. If it is still relevant and reproducable with the latest unstable version, please feel free to reopen with steps to reproduce.

I'm closing this due to inactivity. If it is still relevant and reproducable with the latest unstable version, please feel free to reopen with steps to reproduce.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#844
No description provided.