[Kolab-devel] [issue4719] Freebusy: all-day event declined if the day after has another all-day event

Emanuel Schuetze issues at kolab.org
Fri Mar 25 13:00:18 CET 2011


Tested with Kontact enterprise35 20110321.6842210 and Kolab Server 2.2.4:

1. Create new all-day event E1 (e.g. 20110331).
   Invite resource R (invitation policy: reject if conflicts).
2. Sync -> R accepted invitation for E1.
3. Create new all-day event E2 - one day _before_ E1 (here: 20110330).
   Invite R.
4. Sync -> R _declined_ invitation for E2.

Expected: R should accept E2!

5. Modify E2 to E2': Disable all-day event and enter time 0:00h-23:59h, same
date (here: 20110330).
6. Sync -> R accepted invitation for E2'.

7. Create new all-day event E3 - one day _after_ E1 (here 20110401).
   Invite R.
8. Sync -> R accepted invitation for E3.


=> Seems to be a bug in freebusy if an all-day event is created one day before
an existing all-day event.

----------
assignedto: wrobel
keyword: freebusy, server
messages: 27641
nosy: emanuel, martin, thomas, wickert, wilde, wrobel
priority: urgent
status: unread
title: Freebusy: all-day event declined if the day after has another all-day event

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4719>
______________________________________




More information about the devel mailing list