After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 558363 - Evolution: Appointments reminder window lost on logout + login (reminder data loss)
Evolution: Appointments reminder window lost on logout + login (reminder data...
Status: RESOLVED DUPLICATE of bug 409805
Product: evolution
Classification: Applications
Component: Calendar
2.26.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
evolution[kill-bonobo]
Depends on:
Blocks:
 
 
Reported: 2008-10-29 09:25 UTC by Nick Jenkins
Modified: 2014-07-05 18:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Nick Jenkins 2008-10-29 09:25:27 UTC
What happens:
* I get a reminder dialog for an appointment that is due. I do not close or dismiss the reminder. I want the reminder.
* I log out.
* I log back in, and restart evolution.
* Hours later I get another reminder for another separate appointment.
* My original reminder is gone, destroyed, lost. I never see it again. 

What should happen:
* My reminders should only ever go away if I dismiss them, or if I snooze them (in which case they should come back after the specified period of time).
* If I log back in, and there are reminders which I have not dismissed, then they should appear again, and they should keep on appearing indefinitely until I explicitly dismiss them. The only way reminders should go away permanently is I take an explicit action to dismiss that reminder.

Comment:
* Reminders about events that affect you is exceedingly useful data to users, and losing such a reminder is (to me) absolutely a type of data loss.
* Outlook gets this right. Reminders persist forever until you snooze or dismiss them. This is the IMHO the correct behaviour.

Other information:
Comment 1 Jean-François Fortin Tam 2014-07-05 18:02:54 UTC

*** This bug has been marked as a duplicate of bug 409805 ***