View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002687SOGoWeb Calendarpublic2014-03-27 14:122014-03-28 10:25
Reportervendafo Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Platform[Server] LinuxOSDebianOS Version6 (Squeeze)
Product Version2.2.2 
Summary0002687: Wrong end date in all-day event across a day of change to summer time
Description

This is the first time I am submitting a bug report, so please excuse me if I am not doing it exactly the right way.

On the web calendar, with the timezone set to Europe/Paris in the user preferences, creating an all-day event from March 30 to March 31 (2014) leads to an event displayed from March 30 to March 30 only.

Additional Information

The server timezone is Europe/Berlin so that the current time during the tests was CET.

It seems to be related to the fact that on the 30th of March, the time switches to summer time, as all-day events that do not cross the 31/03/2014 00:00 date do not have this problem as shown in the few examples below.

Additionally, the ICS data that can be downloaded from the web calendar reveal the same issue, so it seems that the problem lies in the creation of the event.

Here are a few examples of events that I have tried. The numbers are the dates (in March 2014, except where otherwise specified). A star denotes an unexpected behaviour:

Event created -> Displayed -> In ICS entry
28-29 -> 28-29 -> 28-30
29-29 -> 29-29 -> 29-30
29-30 -> 29-30 -> 29-31
30-30 -> 30-30 -> 30-31
30-31 -> 30-30 -> 30-31
24Mar-05Apr -> 24Mar-04Apr -> 24Mar-05Apr

It is always reproducible on the system I have used, but I have not tried it on another system.

TagsNo tags attached.

Activities

onofabio

onofabio

2014-03-27 14:38

reporter   ~0006789

I think is the same problem I submitted months ago

0002297
vendafo

vendafo

2014-03-27 15:02

reporter   ~0006791

Last edited: 2014-03-27 15:03

Hi onofiabio - yes, that looks related. As I understand it:

If I want an all-day event from 28 to 28 (no mess with daylight saving changes) it generates the event with:
DTSTART;VALUE=DATE:20140328
DTEND;VALUE=DATE:20140329
The DTEND reads like "29 March 2014, 00:00" excluded, which makes a 24 hours long event.

Now let's try an event from 30 to 31 March 2014, which is a two-days long event (but with one of the days having 23 hours only). This gives:
DTSTART;VALUE=DATE:20140330
DTEND;VALUE=DATE:20140331
DTEND is not OK to my opinion, since interpreting the date as above makes a 23 hours long event, while 47 hours where expected.
vendafo

vendafo

2014-03-27 15:22

reporter   ~0006792

This bug might be the same as 0002686.
onofabio

onofabio

2014-03-28 10:25

reporter   ~0006798

Hi vendalo... I understand
"The DTEND reads like "29 March 2014, 00:00" excluded, which makes a 24 hours long event."

but I create a all day event on 29 March 2014 (with outlook) and in ics system save:
DTSTART;VALUE=DATE:20140328
DTEND;VALUE=DATE:20140329

so outlook show event on 29 March meanwhile iphone and webmail show on 28 March...

If I follow same steps in webmail... ics contain:
DTSTART;VALUE=DATE=20140329
DTEND;VALUE=DATE=20140329
and all devices show event correctly.

I think this is inconsistent behavior.

Issue History

Date Modified Username Field Change
2014-03-27 14:12 vendafo New Issue
2014-03-27 14:38 onofabio Note Added: 0006789
2014-03-27 15:02 vendafo Note Added: 0006791
2014-03-27 15:03 vendafo Note Edited: 0006791
2014-03-27 15:22 vendafo Note Added: 0006792
2014-03-28 10:25 onofabio Note Added: 0006798