6.0.0-git
2021-06-15

[#15027] Task synchronization from DavX5 causes DTSTART rewrite to UTC
Summary Task synchronization from DavX5 causes DTSTART rewrite to UTC
Queue Horde Groupware
Queue Version 5.2.22
Type Bug
State Unconfirmed
Priority 2. Medium
Owners
Requester horde (at) 2600 (dot) sk
Created 2020-07-22 (328 days ago)
Due
Updated 2021-04-19 (57 days ago)
Assigned
Resolved
Milestone
Patch No

History
2021-04-19 09:15:09 Ralf Lang (B1 Systems GmbH) Comment #3 Reply to this comment
Horde does not save tasks as caldav vtodo components.

It rewrites the whole task caldav item from database content. The 
database does not currently save the event's timezone(s).

So it reads in DTSTART;TZID=Europe/Vienna:20200722T160000 and saves 
that - correctly, if I understand your report.
And it writes out DTSTART:20200722T140000Z, which is also correct.
This is form 2 https://tools.ietf.org/html/rfc5545#section-3.3.5


2020-11-02 10:21:13 horde (at) 2600 (dot) sk Comment #2 Reply to this comment
Is there any change someone could take a look on this?
2020-07-22 12:36:28 horde (at) 2600 (dot) sk Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ Task synchronization from DavX5 causes DTSTART rewrite to UTC
Queue ⇒ Horde Groupware
Milestone ⇒
Patch ⇒ No
Reply to this comment
When synchronizing tasks via CalDAV, Horde rewrites DTSTART of all 
tasks to UTC and disregards the original timezone, for example:

data sent to Horde:
...
DTSTART;TZID=Europe/Vienna:20200722T160000
...

gets immediately rewritten to:

...
DTSTART:20200722T140000Z
...

and then synced back to the external client

I don't understand why Horde rewrites the timezone.
The timezone set in Horde settings matches the timezone of the 
external calendar.
Is it possible for horde to leave the timezone as is when synchronizing tasks?

Saved Queries