back-end is ready but we still need to insert alarms into the queue during sync and when creating new events.
There is patch pending for syncing alarms from the server but we still don't offer a ui to edit/create them locally this is an issue to address that part of notifications.
blocking-basecamp: --- → ?
Summary: insert alarms into db & show ui. → Add 'alarm' editing capabilities.
Marked minus as it is a functionnality, get approval
This has an associated user story that is still open, can I get clarification if this is or is not blocking? If its not blocking we should mark it OOS ? After my current list of blockers this is a feature I think we need for v1
blocking-basecamp: - → ?
For context, this is user story CALENDAR-017.
Per Dietrich on an email thread, this has been confirmed out of scope.
blocking-basecamp: ? → ---
[TEF_REQ] as Feature required for TEF build.
Whiteboard: [email@example.com][LOE:S] → [firstname.lastname@example.org][LOE:S], interaction [UX-P1], [TEF_REQ]
Now being tracked in bug 838031.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 838031
Off by one...
Duplicate of bug: 838032
verified bug duped correctly via unagi device build 20130212070205 Dec 5th Kernel
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.