Closed
Bug 496528
Opened 16 years ago
Closed 16 years ago
Multiple alarms wrongly assigned to recurrence events
Categories
(Calendar :: Alarms, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 494140
People
(Reporter: post, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10
Build Identifier: Calendar/1.0pre
Due to entry #353492 there is a multiple alarm feature in the calendar software. This feature is buggy in regard of recurrence (repeating) events. If you use exceptions (e.g. change one item in the event series to other alarms) Sunbird cannot distinguish which alarms apply to which events in the series.
Looking into cal_alarms table there is nothing one can use to identify the corresponding item in cal_events or cal_recurrence -- all have the same id.
Reproducible: Always
Steps to Reproduce:
1. Create an recurrence item with two alarms (15min and 10min before)
2. Change one item in the series and change alarms to "5min before"
3. Now move the 10min alarm from base entry to exception entry
Depending on the order of the three alarm values (might change it in the steps above) you will get the same database content.
Actual Results:
wrong alarms
Expected Results:
correct alarms
Comment 1•16 years ago
|
||
Identical to Bug 494140?
Reporter | ||
Comment 2•16 years ago
|
||
Maybe. It is at least related. The problem is the data format in cal_alarms. There seems to be no way to detect which alarms are related to which event/exception (for recurring events). Sunbird holds some information in memory so you will see the real problem not before restart.
I think it is ok to mark this as duplicate.
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•