[kontact] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage

[Bernhard E. Reiter]

https://bugs.kde.org/show_bug.cgi?id=481024

--- Comment #10 from Bernhard E. Reiter <bernhard at intevation.de> ---
I also find that the regression is a major one. (I've reported this in
https://bugs.kde.org/show_bug.cgi?id=452264 among other significant usability
problems.).

To add more use cases: 
### saving working time shortly before a meeting
 * I have many meetings where the reminder is 15 minutes, so I can prepare.
 * When this is checked I delay up to 2 minutes before the appointment, 
 * and then I have the remaining minutes to completely concentrate on something
else until the alarm rings when I get up and walk to the meeting room. 
 * This I gain 12-8 minutes of working time.

### using several computers
 * I have at least three computers with Kontact, that all sync their
appontments (using the stone-old Kolab 2 format for historical reasons).
 * When working from home once a week, I have to click away all appointments
that have been there since last starting kontact on this machine.
 (This is not a delay use case, but... I mention it because:)

The old kontact/korgac  saved the delay in the internal memory and did not sync
it on the machine.

A property what would really improve the situation would be to sync the fire
time of reminders to the servers
and thus also record a potential new delay . So in @Flossy Cat's use case a
delay for 3 days or so would be in the backup
and also working across synced machines.

I am not sure if the current status of the iCalender format - which is often
used nowadays - allows it. It might.

## User Interface
What about if the desktop notifications bring up a special korganizer/kontact
view that holds all fired alarms for appointments, tasks and so on with options
that allow at least what the old overview did and a compact overview? (Just an
idea.)

-- 
You are receiving this mail because:
You are the assignee for the bug.