[Kolab-devel] [issue4436] free/busy interval is often too low

[Thomas Arendsen Hein]

New submission from Thomas Arendsen Hein <thomas at intevation.de>:

Currently (as of server 2.2.4) the default value for free/busy interval
(kolabFreeBusyFuture) is 60 days. This is very often too short, because users
might want to book resources more than 60 days in advance.
The value can be configured per account in LDAP, so I suggest the default should
be higher, because the admin can still lower the value for very busy accounts.

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.

See also kolab/issue3561 (use global kolabFreeBusyFuture setting and make it
configurable via web admin)

----------
assignedto: cwickert
keyword: filter, freebusy, server
messages: 25564
nosy: cwickert, martin, thomas, wilde, wrobel
priority: bug
status: unread
title: free/busy interval is often too low

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