572111 - Alarms set more than 1 month before the item start date will not fire until 1 month before start date

Status: RESOLVED DUPLICATE of bug 1140035

(Calendar :: Alarms, defect)

Description

[daniel.wedewardt]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4

we set up events in lightning local calendar for cell-phone-contract cancellation periodes. We entered the contract signing date as start date (e.g. 15.06.2008), the periode how long the contract will occur (e.g. every 24 month), set a reminder to 100days before occurence date (in this case 100days before 15.06.2010). We also set this event as an all-day-event and invited the person in company how belongs to this cell-phone-contract.

Unfortunately the reminder occured one month before 15.06.2010 and not 100days what result in an unwanted contract continuation.

Reproducible: Always

Steps to Reproduce:
1. create an event
2. set as an all day event
3. set a starting date
4. set an invitation 
5. set a custom repeat interval of 24month
6. set a custom reminder to 100 days before start date
Actual Results:  
reminder/alarm appear 1month before start date

Expected Results:  
reminder/alarm should appear 100days before

can provide an exported ICS File
This happend several times at our side in diffrent versions

Comment 1

[daniel.wedewardt]

Attachment: exported event

This event was created as described in bug report in a new local calendar. the calendar was exported afterwards.

Comment 2

[Martin Schröder [:mschroeder]]

Daniel, is this still an issue using the recently released Lightning 1.0?

Comment 3

[daniel.wedewardt]

Hi,
meanwhile we switched to GoogleApps Calendar and Google only supports 28days/4weeks reminder max. Workaround is: create two events. 

==> Can not reproduce this issue due to missing business case.
Sorry!

Comment 4

[Matthew Mecca [:mmecca]]

We only expand occurrences 1 month in either direction when loading alarms, so that would cause an alarm more than a month before not to fire until 1 month before the start date.

I suspect the 1 month range limit would be a WONTFIX for performance reasons, but in that case we should prevent users from entering values higher than that in the dialog.

Comment 7

[Peter Weilbacher]

As you didn't manage to fix this somehow (either really fix or as suggested in comment 4), can you at least put this in release notes somewhere so that users are alerted of this?