Closed Bug 816774 Opened 13 years ago Closed 13 years ago

[EMAIL] Launch Email App from a new email notification: No notification for a new email message was received.

Categories

(Firefox OS Graveyard :: Gaia::E-Mail, enhancement)

ARM
Gonk (Firefox OS)
enhancement
Not set
normal

Tracking

(blocking-basecamp:-, b2g18-)

VERIFIED DUPLICATE of bug 796751
blocking-basecamp -
Tracking Status
b2g18 - ---

People

(Reporter: mlevin, Unassigned)

Details

(Whiteboard: testrun 4, interaction [UX-P1], [TEF_REQ], PRODUCT-FEATURE)

Unagi Build ID: 20121129071415 Steps: 1. Prerequisites: Have an email account set up on the device. 2. With the app closed receive an email to one of the email accounts on the device. Expected: A notification for a new email message is received. Actual: No notification was received. Had to open the app and pop the account to receive the new e-mail. Tested both a gmail and yahoo accounts set up on the Unagi.
Noming for b2g.
blocking-basecamp: --- → ?
removing nom: it turns out I forgot that email notification is no longer a v1 issue : bug 804911
blocking-basecamp: ? → -
Issue foes repro on Build 20130104070203. No notification given when new email is received
Whiteboard: testrun 2
Issue repros on unagi build 20130115070201 Kernel from Dec 5th
OS: Windows 7 → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Blocks: 834664
No longer blocks: 834664
Whiteboard: testrun 2 → testrun 2, interaction [UX-P1], [TEF_REQ]
IIRC Notifications are not supported for Email as periodic pollings are not supported in V1
Whiteboard: testrun 2, interaction [UX-P1], [TEF_REQ] → testrun 2, interaction [UX-P1], [TEF_REQ], PRODUCT-FEATURE
Issue repros. No notification when receiving a new email. Build ID: 20130130070201 Kernel: Dec 5 Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/4593f3e765eb Gaia f7f5a0cd17e3d04308cc5850b254947e127122b9
Whiteboard: testrun 2, interaction [UX-P1], [TEF_REQ], PRODUCT-FEATURE → testrun 4, interaction [UX-P1], [TEF_REQ], PRODUCT-FEATURE
I think this is fixed on master at least for the sound. marking it as enhancement for future. disabling v1.
Severity: normal → enhancement
tracking-b2g18: --- → ?
Comment 6 makes it sound like this is OOS for v1 so minusing for tracking, renom for version.next
Can we get product input on whether or not this is a required v1 feature (keeping in mind comment 6)?
Flags: needinfo?(ffos-product)
(In reply to Andrew Overholt [:overholt] from comment #10) > Can we get product input on whether or not this is a required v1 feature > (keeping in mind comment 6)? This is not a required v1 feature and was very explicitly out-of-scoped. This is one of the many bugs that were filed because the moztrap cases got out of sync with the features.
(In reply to Andrew Sutherland (:asuth) from comment #11) > > This is not a required v1 feature and was very explicitly out-of-scoped. Correct - it is being examined for a future release.
Flags: needinfo?(ffos-product)
Appears to be a dupe of 796751
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Verified as a dupe of bug 796751
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.