touch-packages team mailing list archive

[Nekhelesh Ramananthan <krnekhelesh@xxxxxxxxx>]

Public bug reported:

Alarms API should expose a unique permanent alarm ID that clock app can
use to open an alarm instead of just the alarm index that varies based
on the alarm date dynamically.

Use Case: Bug 1387210 Indicator-datetime will pass the QOrganizerItemId
(unique alarm ID) to clock app when the user clicks on an alarm in the
indicator-datetime. But the current Alarms API does not allow clock app
to open the alarm using that unique ID which results in clock app not
knowing which alarm to show to the user.

** Affects: ubuntu-ui-toolkit (Ubuntu)
     Importance: High
     Assignee: Zsombor Egri (zsombi)
         Status: Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1426361

Title:
  Alarms API should expose a unique permanent alarm ID that clock app
  can use to open an alarm

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Alarms API should expose a unique permanent alarm ID that clock app
  can use to open an alarm instead of just the alarm index that varies
  based on the alarm date dynamically.

  Use Case: Bug 1387210 Indicator-datetime will pass the
  QOrganizerItemId (unique alarm ID) to clock app when the user clicks
  on an alarm in the indicator-datetime. But the current Alarms API does
  not allow clock app to open the alarm using that unique ID which
  results in clock app not knowing which alarm to show to the user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1426361/+subscriptions