View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001092||SOGo||Backend Calendar||public||2011-01-24 09:33||2011-03-23 20:17|
|Fixed in Version||1.3.6|
|Summary||0001092: Declining a single occurrence of a recurring event leads to declining of the master event in organizer's calendar.|
When you decline an occurrence of a recurring event through Thunderbird ( Inverse Lightning + SOGo Integrator and Connector), then in the organizer's calendar, the master event gets declined (which had the "ACCEPTED" status before), while the status for the occurrence remains "NEEDS-ACTION". In the attendee's calendar, however, the behavior is as it should be - the master event remains "ACCEPTED", and the occurrence status is "DECLINED".
Reproducible as follows:
1) Create a recurring event, Event X, as user foo, and invite bar.
2) Bar accepts Event X.
3) foo changes a particular occurrence.
4) bar rejects the change.
5) In bar's calendar, occurrence appears as rejected, and the master event as accepted. In foo's calendar occurrence's status remains "NEEDS-ACTION" while master event gets declined.
|Tags||No tags attached.|
There's already a problem at step 3 : if foo changes the time of one occurrence, the PARTSTAT of bar for this new occurrence stays to ACCEPT in foo's calendar, while it is properly reset to NEEDS-ACTION in bar's calendar.
Everything is correct when performing the same scenario in the Web interface.
Fixed with http://mtn.inverse.ca/revision/diff/11c0941cac8926d96e43efabe282a5d3d549d0c9/with/3931b3fc847a4504339f11bcd48a3ea417c822b0
|2011-01-24 09:33||alcy||New Issue|
|2011-02-11 01:48||francis||Note Added: 0002096|
|2011-03-23 20:17||ludovic||Note Added: 0002292|
|2011-03-23 20:17||ludovic||Status||new => resolved|
|2011-03-23 20:17||ludovic||Fixed in Version||=> 1.3.6|
|2011-03-23 20:17||ludovic||Resolution||open => fixed|
|2011-03-23 20:17||ludovic||Assigned To||=> ludovic|