Bug 191086

Summary: wish: read-only calendars should not cause reminder alarms to fire (or this capability should be configurable on a calendar by calendar basis)
Product: [Applications] korganizer Reporter: doc.evans
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: wishlist CC: chris.kerr, david.alston, gjditchfield
Priority: NOR    
Version: 4.2.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description doc.evans 2009-04-30 00:13:41 UTC 
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

In a business environment, one may want to subscribe to a large number of remote calendars in read-only mode (calendars for colleagues, departments, etc.).

The current korganizer behaviour, however, makes this impractical, because if a colleague places reminders on his calendar (which would be useful for him), korganizer will fire those same reminders on *my* system. If subscribed to calendars from many colleagues, one would be inundated all day with alarms firing, none of which are relevant to *me*.

So either korganizer should simply NOT fire reminder alarms for remote calendars (if I want to be reminded, then I can put a reminder in place on my own calendar), or it should allow for the option of firing reminders on a remote-calendar-by-remote-calendar basis.

(To make the current system even more aggravating, the time at which the alarm is set to fire on the remote read-only calendar may well not be the time that I would want to be reminded of the event.)
Comment 1 gjditchfield 2021-05-12 01:30:29 UTC 
The Folder Properties dialog of each calendar now has a "Block reminders locally" option on the General tab.  Does that satisfy this wish?
Comment 2 Chris Kerr 2021-05-12 04:07:05 UTC 
(In reply to gjditchfield from comment #1)
> The Folder Properties dialog of each calendar now has a "Block reminders
> locally" option on the General tab.  Does that satisfy this wish?

Yes. Thank you!
Comment 3 gjditchfield 2021-07-19 01:33:05 UTC 
*** Bug 281125 has been marked as a duplicate of this bug. ***