[Kolab-devel] [issue4481] Automatically trigger a resource when booking in case its free/busy information is too old

Gunnar Wrobel issues at kolab.org
Thu Jul 22 16:15:40 CEST 2010


New submission from Gunnar Wrobel <p at rdus.de>:

>From issue4436:

Additionally the free/busy list might be generated e.g. 50 days in the past (at
the time the last update to the calendar folder was made), so the current list
only covers the following 10 days, not 60 days.
I suggest triggering the free/busy list before tentatively accepting (see also
/issue3562 (tentative answer when inviting outside of free/busy interval is
confusing)) if it is older than X days, where X could be somewhere between 1 and
kolabFreeBusyFuture/4.

----------
assignedto: wrobel
keyword: filter, freebusy, server
messages: 25841
nosy: cwickert, martin, thomas, wilde, wrobel
priority: bug
status: chatting
title: Automatically trigger a resource when booking in case its free/busy information is too old

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




More information about the devel mailing list