unity-api-bugs team mailing list archive

[Giorgio Venturi <giorgio.venturi@xxxxxxxxxxxxx>]

There's one more edge use case: an alarm set for 10:00, one for 10:01
Desired solution:
1) The user picks the phone at 10:00 and sets the alarm off, then he has to do it again at 10:01
2) The user picks the phone at 10:02 and he can set off both of them at the same time

I would suggest the following approach:
If 2 or more alarms have been triggered, the notification at any time will display:
  Title: 2 Alarms
  Subtitle: [Label 1] 10:00, [Label 2] 10:01 


** Changed in: ubuntu-ux
       Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Indicator Date and Time.
https://bugs.launchpad.net/bugs/1358890

Title:
  Need better usability when two alarms kick at the same time

Status in The Date and Time Indicator:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed

Bug description:
  A cousin of bug #1354406

  Some of the early testers are hitting a use case that we didn't
  account for, that of multiple alarms set for the same time.

  Indicator-datetime currently tries to pull up notifications for, and
  play sounds for, both notifications. That's happening by accident and
  is clearly not the right approach.

  I can think of a couple of approaches we might take:

  (1) Queue the alarms such that only one triggers at a time. This has
  the advantage of being simple, both in concept and in code. I'm not
  certain this is the most user-friendly approach, as it could be
  frustrating have to dismiss a queue of alarms.

  (2) Somehow fold multiple alarms together. This has the advantage of
  being friendlier to the user as only a single snooze/dismiss prompt
  would be given. However it opens other questions, e.g. which of the
  alarms' sounds should play?

  Of these two I slghtly prefer (1) for its simplicity; however, neither
  of these options seems perfect and I'm hoping Design may have a better
  suggestion

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1358890/+subscriptions