Calendar:Deprecated:Feature Requirements/Roadmap Review: Difference between revisions

Calendar:Deprecated:Feature Requirements/Roadmap Review (view source)

285 bytes removed , 1 September 2005

Confirmed users

503

edits

@@ Line 25: / Line 25: @@
 * Alarms give a snooze function (remind me in X minutes, snooze past event start, remember status when Calendar is turned off).
 * Snoozing alarms should persist. If you snooze an alarm, and then shut Calendar down, it should remember that the alarm was snoozed.
-* Alarms that have passed when PC has been off will go off on Calendar start-up.
+* Alarms that have passed when calendar/sunbird was not running will go off on Calendar start-up.
+* Alarms can be turned on or off per calendar.
 * Alarms can be turned off globally.
-* Alarms can be set X minutes, days or weeks before the event in the form of pop-up or email.
+* Alarms can be set X minutes, days or weeks before the event.
 * The user should be able to snooze events for a certain time, and for a certain amount of time before the event. [Remind me again [___] (mins / hrs / days) (from now / before event)] PARTIALLY COMPLETE (just regular snooze)
 * The user should be able to see all the alarms that have not gone off.
-* The user should be able to have multiple alarms for the same event. You could have one to remind you to prepare for the event, and another that the event is occurring.
-* Alarms must go off when calendar is not running.
-* Email that is sent out needs to be configurable (e.g include notes from event, "%user wrote:")
 == Associating ==