View Issue Details

IDProjectCategoryView StatusLast Update
0002336SOGoWeb Generalpublic2016-07-06 06:59
Reporterryacketta Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
Status newResolutionopen 
Product Version2.0.5a 
Target Versionsoon 
Summary0002336: Meeting Alarms triggered at wrong times
Description

Several users have reported issues with receiving alarms for meetings that are in the future, for example user received an alarm for a meeting on 7/3 - 7/4 with an alarm of -1D.

Additional Information

DTSATRT;VALUE=DATE:20130703
DTEND;VALUE=DATE:20130704

TRIGGER;X-WEBSTATUS=triggered;VALUE=DURATION:-P1D
ACTION:DISPLAY

TagsNo tags attached.

Activities

2013-06-06 09:44

 

SOGo-Alarm.png (35,224 bytes)   
SOGo-Alarm.png (35,224 bytes)   
ryacketta

ryacketta

2013-06-06 09:44

reporter   ~0005641

BEGIN:VCALENDAR
PRODID:-//Inverse inc./SOGo 2.0.4b//EN
VERSION:2.0
BEGIN:VEVENT
UID:570E-518A9900-122B-7E1B2280
SUMMARY:Activate Crumb/Crane Summer hrs 2
LOCATION:Crumb 232-Jims office
CLASS:PUBLIC
PRIORITY:1
CATEGORIES:Admin work
CREATED:20130508T182821Z
DTSTAMP:20130508T182821Z
LAST-MODIFIED:20130508T182821Z
BEGIN:VALARM
TRIGGER;X-WEBSTATUS=triggered;VALUE=DURATION:-P1D
ACTION:DISPLAY
END:VALARM
DTSTART;VALUE=DATE:20130703
DTEND;VALUE=DATE:20130704
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR

ryacketta

ryacketta

2013-06-06 09:47

reporter   ~0005642

Another oddity I just noticed is SOGo reports 2.0.4b (in about and above ICS) while we have 2.0.5a installed. SOGo and memcached restarted with same result.

rpm -qa | grep sogo
sogo-tool-2.0.5a-1.centos6.x86_64
sogo-ealarms-notify-2.0.5a-1.centos6.x86_64
sogo-2.0.5a-1.centos6.x86_64

rpm -qi sogo
Name : sogo Relocations: /usr
Version : 2.0.5a Vendor: http://www.inverse.ca/
Release : 1.centos6 Build Date: Tue 16 Apr 2013 03:54:09 PM EDT
Install Date: Thu 18 Apr 2013 06:18:24 AM EDT Build Host: shiva
Group : Productivity/Groupware Source RPM: sogo-2.0.5a-1.centos6.src.rpm
Size : 14202180 License: GPL
Signature : (none)
Packager : Wolfgang Sourdeau <support@inverse.ca>
URL : http://www.inverse.ca/contributions/sogo.html
Summary : SOGo

ludovic

ludovic

2014-09-12 15:18

administrator   ~0007502

Last edited: 2014-09-12 15:19

Problem here is that SOGo and Lightning are stupid when it comes to alarms on all-day events.

If you set an all-day event on Friday, September 12th 2014 and set a reminder 1 day before, it'll actually set the alarm, for America/Montreal to Wednesday at 8h00pm.

That is because it does September 12th - 1 day, which gives September 11th (midnight), minus the DST offset, so that gives September 10th at 8pm.

My guess is that we should do something like Apple iCal does - ie., have specific corner cases for alarms on all-day events. We could PREVENT the user from using the minutes/hours reminders and only let him/her use the 'days' ones'.

We could then use also the "Day start time" user preference to set the alarm accordingly.

So in my example above, if I have my "Day start time" set to 8h00am, the alarm would popup on Thursday, 8h00am.

Christian Mack

Christian Mack

2016-07-05 11:43

developer   ~0010469

Any update?

ludovic

ludovic

2016-07-06 06:59

administrator   ~0010471

This should be targeted to v3 only.

Issue History

Date Modified Username Field Change
2013-06-06 09:44 ryacketta New Issue
2013-06-06 09:44 ryacketta File Added: SOGo-Alarm.png
2013-06-06 09:44 ryacketta Note Added: 0005641
2013-06-06 09:47 ryacketta Note Added: 0005642
2014-09-05 14:21 ludovic Target Version => 2.2.9
2014-09-12 15:18 ludovic Note Added: 0007502
2014-09-12 15:19 ludovic Note Edited: 0007502
2014-09-23 14:21 ludovic Severity major => feature
2014-09-23 14:21 ludovic Target Version 2.2.9 => soon
2016-07-05 11:43 Christian Mack Note Added: 0010469
2016-07-06 06:59 ludovic Note Added: 0010471