Red Hat Bugzilla – Bug 652521
Remember alarm's last notified per calendar
Last modified: 2013-10-06 21:49:21 EDT
Created attachment 459920 [details]
patch based on upstream code
Description of problem:
Most visible with calendars requiring passwords, but users don't want to store
calendar password within evolution, they rather enter it each start.
For such calendars the alarm notification is not run on start, but rather
later, when the password is known, which means all the alarms in time of
not-active can be lost.
Thus I would suggest to store last-notification time per calendar, say as a
property in an ESource, and when not known, then choose date say a week back,
to rather re-notify for older events than lost them at all.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create an appointment which pops up in 20mins, with alarm 15mins ahead
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 5, and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.