Closed
Bug 799566
Opened 12 years ago
Closed 11 years ago
Add 'alarm' editing capabilities.
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect)
Firefox OS Graveyard
Gaia::Calendar
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 838032
People
(Reporter: jlal, Unassigned)
References
Details
(Whiteboard: [mentor=jlal@mozilla.com][LOE:S], interaction [UX-P1], [TEF_REQ])
back-end is ready but we still need to insert alarms into the queue during sync and when creating new events.
Reporter | ||
Comment 1•12 years ago
|
||
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.
Updated•12 years ago
|
blocking-basecamp: ? → -
Comment 2•12 years ago
|
||
Marked minus as it is a functionnality, get approval
Reporter | ||
Comment 3•12 years ago
|
||
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: - → ?
Flags: needinfo?(clee)
Comment 4•12 years ago
|
||
For context, this is user story CALENDAR-017.
Comment 5•12 years ago
|
||
Per Dietrich on an email thread, this has been confirmed out of scope.
blocking-basecamp: ? → ---
Flags: needinfo?(clee)
Reporter | ||
Updated•11 years ago
|
Whiteboard: [mentor=jlal@mozilla.com][LOE:S]
Comment 8•11 years ago
|
||
[TEF_REQ] as Feature required for TEF build.
Whiteboard: [mentor=jlal@mozilla.com][LOE:S] → [mentor=jlal@mozilla.com][LOE:S], interaction [UX-P1], [TEF_REQ]
Comment 9•11 years ago
|
||
Now being tracked in bug 838031.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Comment 10•11 years ago
|
||
Off by one...
Comment 11•11 years ago
|
||
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.
Description
•