| Summary | Snooze and dismissal for Sunbird/Lightning |
| Queue | Kronolith |
| Queue Version | Git master |
| Type | Enhancement |
| State | Duplicate |
| Priority | 2. Medium |
| Owners | |
| Requester | spamstop1 (at) terriertech (dot) com |
| Created | 04/29/2011 (5180 days ago) |
| Due | |
| Updated | 06/30/2011 (5118 days ago) |
| Assigned | |
| Resolved | 06/30/2011 (5118 days ago) |
| Milestone | |
| Patch | Yes |
State ⇒ Duplicate
implemented for Kronolith 2 anyway.
Priority ⇒ 2. Medium
New Attachment: Snooze.patch
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Snooze and dismissal for Sunbird/Lightning
Type ⇒ Enhancement
State ⇒ New
Ticket #7470then realised that ticket wasfor the 2.3 queue.
I could not see a good solution to the snooze/dismiss problem without
storing the snooze info with the event. Therefore, I added an
event_snooze varchar column to kronolith_events. See attached patch
(relative to 3.0.2-git).
This seems to work for dismiss, snooze (including multiple successive
snoozes, in limited testing), and recurring events (if the LASTACK
occurs before one occurrence, then Thunderbird views the following
occurrence as not ACKed). It also seems to work OK on multiple
Thunderbird clients in the same timezone, i.e. snoozing on one client
will auto-dismiss the alarm on other clients next time they reload the
calendar.
Hope this helps.