http://bugzilla.novell.com/show_bug.cgi?id=561218 http://bugzilla.novell.com/show_bug.cgi?id=561218#c0 Summary: evolution calendar does not set alarm for appointment accepted via iCal Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: alext@novell.com QAContact: qa@suse.de Found By: --- Blocker: --- When accepting appointments via iCal, especially those generated from GW, the reminder alarm for the appointment is not set and evolution does not allow the end user to set an alarm for that appointment. When accepting appointments generated with evolution, if the original appointment has an alarm set, then the accepted appointment also has an alarm; however, if the original appointment does not have the alarm set, then the accepted appointment does not have the alarm set. For an appointment that does not have a reminder alarm set, there is no way to override the alarm setting and set an alarm in evolution. The only workaround I've found is to create another, local, appointment at the same time as the accepted appt. and set the alarm in the local one. This is very cumbersome since you end up having to create a local appointment for every appointment accepted. Three suggestions: 1) Allow user to override the alarm for any appointments (currently alarm is grayed out for appts. that do not have an alarm). This will let the user decide on whether they want an alarm on an appointment or not, rather than the sender of the appointment. The user is who is affected by the alarm, not the sender, so this makes logical sense, IMHO. 2) Fix iCal interpretation of GW-generated appointments to have the alarm active. 3) Perhaps all appointments accepted via iCal should default to having the reminder alarm on, rather than not. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.