851041 - "RANGE=THISANDFUTURE" modifier not honored

Status: UNCONFIRMED

(Calendar :: General, defect)

Description

[accounts.oss]

Upon receipt of an update to multiple occurrences of a recurring event, only the first instance is modified whereas the subsequent ones are left unchanged. Example:

original event

BEGIN:VEVENT
UID:E0A9566FDA68D8A8C1257B2D007F7013-Lotus_Notes_Generated
DTSTAMP:20130313T231202Z
DTSTART;TZID=Europe/Rome:20130314T001500
DTEND;TZID=Europe/Rome:20130314T011500
SUMMARY:test3
RRULE:COUNT=3.0;FREQ=DAILY;INTERVAL=1
SEQUENCE:0
STATUS:CONFIRMED
TRANSP:OPAQUE
ORGANIZER....
END:VEVENT

this creates three meetings on March 14th, 15th and 16th, respectively, at 0015 to 0115 CET. 

The following update

BEGIN:VEVENT
UID:E0A9566FDA68D8A8C1257B2D007F7013-Lotus_Notes_Generated
DTSTAMP:20130313T234921Z
DTSTART;TZID=Europe/Rome:20130315T014500
DTEND;TZID=Europe/Rome:20130315T024500
SUMMARY:test3
RECURRENCE-ID;RANGE=THISANDFUTURE:20130314T231500Z
RDATE;TZID=Europe/Rome;
 VALUE=PERIOD:
 20130315T014500/20130315T024500,20130316T014500/20130316T024500
SEQUENCE:1
STATUS:CONFIRMED
TRANSP:OPAQUE
ORGANIZER...
END:VEVENT

should reschedule the instances of March 15th and 16th to take place from 0145 to 0245 CET. The recurrence ID field correctly identifies the second occurrence of the meeting and the RDATE field contains the updated times for the last two occurrences.

Expected behaviour: reschedule both the occurrence of the 15th and of the 16th.
Detected behaviour: only the March 15th occurrence is rescheduled.
Reproducible: always

Comment 1

[Stefan Sitter [:ssitter]]

Lightning or the libical library or both doesn't support this advanced feature yet. 
Compare to existing bug 320178.