Event start date not in the recurrence pattern?

It came from Outlook users but we’ve found out it’s indeed a real issue. For example assume it is Thursday and you create a new event that is recurring weekly on Fridays. Did you ever wanted such an event to occur on the day it has been created? I think if you want Fridays that’s Fridays only. Of course you could add an exception later, so the event is moved to another day for a specific occurrence, but that’s another story.

Now if you create such an event, first occurrence will be on this Thursday and Friday. I believe in most cases this is not an intended behavior. It also creates confusion if you use more than one client and they handle this case differently. You will see a difference in displaying your calendar across clients.

This is how Kolab works and for example Thunderbird Lightning too, but not Outlook. In Kolab we’ll solve this by additional checkbox and will default to Outlook behavior. If checked, the start date of the event will be aligned with the first occurrence of the event (on or after the original creation date).

event-start

Improvement in (free-busy) availability finder

When planning a meeting with other people in your organization you use Availability Finder widget. It’s granularity from the beginning was one hour, no less no more. On the other hand in Calendar view you could configure that granularity, i.e. number of slots in an hour.

My changeset that awaits a review will fix this inconsistence. As you see on the picture below the same granularity will be used both in calendar view and availability finder.

Without my fix the whole slot is busy/tentative no matter how long the existing events of the user would take. In this case the user is free from 08:00 to 08:30 and busy from 08:30 to 09:00. With my fix the whole one hour slot will be split into “sub-slots”, so you can plan the new event easier and with more precise timing.

fbfinder

This change also fixes issues of the selection box (the dark rectangle at 06:30-07:00 above). Its moves on Previous/Next Slot action were a little bit unexpected sometimes. Now it’s more precise and uses the same granularity.