| Summary | All day events expanding to two days |
| Queue | Kronolith |
| Queue Version | 4.1.1 |
| Type | Bug |
| State | Duplicate |
| Priority | 2. Medium |
| Owners | |
| Requester | neil.watson (at) ulr (dot) co (dot) uk |
| Created | 07/15/2013 (4373 days ago) |
| Due | |
| Updated | 07/24/2013 (4364 days ago) |
| Assigned | |
| Resolved | 07/24/2013 (4364 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
Bug: 11976BEGIN:VCALENDAR
VERSION:1.0
PRODID:vCal ID default
TZ:+00:00
BEGIN:VEVENT
UID:content://com.android.calendar/events/47026
DTEND:20130719
DTSTART:20130718
COMPLETED:20130719T000000Z
SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:Test event
STATUS:TENTATIVE
END:VEVENT
END:VCALENDAR
When i mail this as a ics to myself it is correctly displayed
displayed in IMP as:
Start: 18/07/2013 0:00
End: 18/07/2013 23:59
Summary: Test event
But kronolith gives it a date of:
From 18/07/13
To 19/07/13
meaning if i amend it in kronolith the event expands over two days
Priority ⇒ 2. Medium
New Attachment: cal oddness.xls
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ All day events expanding to two days
Type ⇒ Bug
State ⇒ Unconfirmed
after editing in an external client (both active-sync and CalDAV).
I have attached the database entries for before and after the editing
takes place, line 2 is a kronolith created line, line 3 is after
editing in an external client.
You can see that the "end_event" field is now set for the next day so
if a user amends this again in kronolth the event is then spread
across two days instead of the original one