Closed Bug 561915 Opened 14 years ago Closed 13 years ago

Alarm still active for old event date after rescheduling event to future date

Categories

(Calendar :: Sunbird Only, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 360916

People

(Reporter: peter.wilkins, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729)
Build Identifier: 0.9

Event for next day was rescheduled for the same week day and time the following (next) week ... but the alarm (one day in advance) still active for old event date (tomorrow, when it has been rescheduled for tomorrow week).

I will close and restart Mozilla to see if this clears bug...



Reproducible: Always

Steps to Reproduce:
1. schedule future event with alarm "1 day before"
2. reschedule event on day before to future date, save and close event detail
3. alarm observed to be still active for OLD event date and time
Actual Results:  
Alarm still active for originally rescheduled date and time, and not for new date and time

Expected Results:  
Expect alarm to be reset to new date and time baseline

When alarm falsely triggered, do not want to "Dismiss" alarm ... because, obviously, want the alarm to occur based on new time and date baseline ... but (obviously) do not appreciated continued annoyance of alarm for old (rescheduled) event.
Addendum subsequent to closing and re-launch Sunbird:

Bug still apparent ... alarm still remains active for old (original) date and time, even though "Reminder" correctly shows new (rescheduled) event and time.

It then occurred to me that if the alarm is cancelled and then rescheduled, the problem would be resolved (on assumption that error caused by active session data not being correctly updated when event rescheduled).

Accordingly, to test this hypothesis, I then set alarm to "No reminder" (save and close) ... then re-open event and select:

   Reminder: "1 day before"

However, the alarm immediately activated on re-setting alarem (reminder).

Evidently, the only way to resolve this bug in this release is to cancel (Delete Event), then create new event for new date and time.

This is obviously absurd and extremely annoying. 

There is clearly a problem in the alarm (reminder) routine.

I recommend checking the source code to ensure that alarms (reminders) are RELATIVE to CURRENT event date and time.  Based on my observations, it would appear that somewhere buried in the code, the alarm (reminder) date and time is saved as an ABSOLUTE variable (based on original date and time), rather than as a RELATIVE variable (based on an OFFSET from CURRENT event date and time.

I predict that if you look for such and instance, you will find it somewhere...
Did you snoozed the alarm before moving the event, e.g. by pressing the snooze button or closing the reminder dialog? If yes --> Bug 360916.

The current release of Sunbird and Lightning 1.0 Beta 1 allows the creation of relative (e.g. 5 minutes before) and absolute (e.g. 2010-04-28 12pm) reminders. Previous releases support only relative alarms.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.