Comment 10 for bug 1361702

On Wed, Sep 24, 2014 at 4:23 PM, Charles Kerr <email address hidden>
wrote:

> Summary of irc chat:
>
> For RTM:
>
> 1. ubuntu-ui-toolkit will add two tags/categories: (1) "x-canonical-
> alarm" present in all alarms, and also (2) "x-canonical-disabled" in the
> disabled ones.
>
> 2. ubuntu-clock-app will ignore / not show anything with the "x
> -canonical-alarm" tag
>

I'm guessing this should read calendar-app instead? We definitely need to
show alarms in clock.

>
> 3. indicator-datetime will ignore / not kick on alarms with the "x
> -canonical-disabled" tag
>
> 4. indicator-datetime will address High bug #1362341 with the tag
> context discussed here.
>
> Post RTM:
>
> Look for a non-ical solution for clock-app alarms so that these kind of
> magic flags aren't necessary, perhaps an alarm CRUD API in indicator-
> datetime's DBus API.
>
> --
> You received this bug notification because you are subscribed to Ubuntu
> UI Toolkit.
> https://bugs.launchpad.net/bugs/1361702
>
> Title:
> clock-app alarms need to be handled differently from other VTODO
> events
>
> Status in The Date and Time Indicator:
> Triaged
> Status in Calendar application for Ubuntu devices:
> Confirmed
> Status in Ubuntu UI Toolkit:
> Triaged
>
> Bug description:
> When you disable an alarm in the new clock app (with white
> background), it causes the alarm to show up as a calendar event. The
> expected behaviour is to not show up at all.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/indicator-datetime/+bug/1361702/+subscriptions
>