Page MenuHomePhorge
Create Task
Maniphest T653

Fix handling of alarms with "zero duration" (e.g. PT0S)
Closed, ResolvedPublic8 Story Points
Actions

Description

When adding an event with following alarm spec. in iRony:

BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:PT0S
DESCRIPTION:Default Mozilla Description
END:VALARM

it is then converted to:

BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;VALUE=DATE-TIME:19700101T000000Z
END:VALARM

Which means that alarm description is lost and the trigger is wrong.
Another story is if such alarms are handled/displayed correctly by other clients e.g. Roundcube. I'm afraid they might be handled as no-alarm.

OTRS#1012323

Details

Ticket Type
Task

Related Objects
Search...

Event Timeline

machniak created this task.Jul 21 2015, 10:56 AM
machniak raised the priority of this task from to 60.
machniak updated the task description. (Show Details)
machniak added a project: iRony.
machniak changed Ticket Type from Task to Task.
machniak subscribed.
grote added a project: Product Owners.Jul 28 2015, 4:46 PM
grote moved this task from Incoming to In Triage on the Product Owners board.
grote moved this task from In Triage to Ready for Sprint on the Product Owners board.Jul 29 2015, 2:04 PM
grote added a project: Restricted Project.
grote moved this task from Ready for Sprint to In Sprint on the Product Owners board.Jul 29 2015, 2:24 PM
machniak added a comment.Jul 30 2015, 12:24 PM
  1. kolab-syncroton does not support Reminder=0 now, need to be fixed.
  2. There are issues in Roundcube UI. While you can set alarm to "0" when you visit the event again there are small glitches in the alarm description and edit field. The reminder message is not displayed.

BTW, when adding such event via Roundcube the TRIGGER is correctly saved as -PT0M. So, it looks that iRony/SabreDAV is doing something wrong here.

machniak claimed this task.Aug 3 2015, 9:24 AM
machniak edited a custom field.
machniak moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
machniak closed subtask T665: Fix handling of alarms with "zero duration" (e.g. PT0S) as Resolved.Aug 3 2015, 10:54 AM
machniak added a comment.Aug 3 2015, 2:30 PM

I found it's libkolabxml issue, see T670. However, some code alignments and workarounds still needed in libkolab and libcalenaring plugins.

machniak closed subtask T670: Fix handling of alarms with "zero duration" (e.g. PT0S) as Invalid.Aug 3 2015, 4:14 PM
machniak added a comment.Aug 4 2015, 11:41 AM

I'm unable to reproduce the initial issue in Kolab:Development. The TRIGGER property is not broken when importing ics using iRony and then exporting it there.

machniak added a comment.Aug 4 2015, 5:30 PM

Also not reproducable with current KE14 - iRony DAV Server 0.2.8SabreSabre VObject 2.1.3.

machniak mentioned this in rRPKc3d096d104c5: Fix handling of alarms specified as PT0S, PT0M, etc. (T653).Aug 5 2015, 10:40 AM
machniak mentioned this in rRPK957ebdf4662a: Fix bug where alarms set on event start time were displayed on event end time….Aug 5 2015, 12:12 PM
machniak closed this task as Resolved.Aug 5 2015, 12:13 PM
machniak edited projects, added Roundcube Kolab Plugins ; removed iRony.

Fixed also some Kolab plugins issues. I consider this ticket issue fixed.

machniak moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Aug 5 2015, 12:14 PM
machniak reopened subtask T670: Fix handling of alarms with "zero duration" (e.g. PT0S) as Open.Aug 7 2015, 11:02 AM
machniak mentioned this in rRPKf7293f555b69: Fix handling of alarms specified as PT0S, PT0M, etc. (T653).Aug 7 2015, 1:21 PM
machniak mentioned this in rRPKdc0b4bd39ac3: Fix bug where alarms set on event start time were displayed on event end time….