821839 - The number of unread messages is not shown on the Inbox / message list card

Status: RESOLVED DUPLICATE of bug 800402

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

Description

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

## Environment :
Unagi phone, build 2012-12-13

## Repro :
1. launch email app
2. add an email account if one isnt' added already
3. send yourself an email to that account
4. look at the inbox banner


## Expected :
1. unread messages should be indicated with a number in the banner

## Actual :
1. no number indication of how many unread emails 

## Note :

Comment 1

[Mila Davydova]

Unagi, build ID 20121217070202
The number of unread messages is not shown on the Inbox.

Comment 2

[Jeni]

Issue repros in build 20130104070203.  Inbox does not display number of unread messages in header

Comment 3

[amiller]

UCID: email-032
https://moztrap.mozilla.org/results/case/61783/

Comment 4

[mdaniloff]

Repros in Unagi build #20130115070201, Kernel Dec 5

Comment 5

[Jeni]

Issue currently repros.  There is no visual spot on email that shows how many unread messages you have.

Build ID: 20130130070201
Kernel: Dec 5
Gecko  http://hg.mozilla.org/releases/mozilla-b2g18/rev/4593f3e765eb
Gaia   f7f5a0cd17e3d04308cc5850b254947e127122b9

Comment 6

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

cc'ing cyee.  I think it's polish though good to have in a future version and noming it for tracking.

Cyee, please nom if you think it's more vital.

Comment 7

[Lukas Blakk [:lsblakk] use ?needinfo]

Do we have the support built in to v1 for this addition?  Will this be targeted for v1?

Comment 8

[Mila Davydova]

This issue still reproduces on Unagi device
Build ID: 20130225070200
Kernel Date: Dec 5
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/3a5a27992a75
Gaia: 5691a16fff8e1403c75ed9d6f3a443b7e58198c6

TC:https://moztrap.mozilla.org/runtests/run/859/env/305/?pagenumber=1&pagesize=20&sortfield=order&sortdirection=asc&filter-id=2592
UCID: email-032

Comment 9

[Andrew Sutherland [:asuth] (he/him)]

(In reply to Lukas Blakk [:lsblakk] from comment #7)
> Do we have the support built in to v1 for this addition?  Will this be
> targeted for v1?

There's a good chance this will happen as a follow-up to bug 822882 by treating unread as discussed on bug 800402.

We are unlikely to track any work on this bug since it's mainly a bunch of spam about the feature still not existing.

Comment 10

[Lukas Blakk [:lsblakk] use ?needinfo]

Since this feature is not in the required features for v1.1 so not tracking.  If at some point there is a low risk patch available here to go along with this feature making it into a v1-train uplift, please nominate the patch(es) for approval to uplift.

Comment 11

[Andrew Sutherland [:asuth] (he/him)]

(In reply to Andrew Sutherland (:asuth) from comment #9)
> There's a good chance this will happen as a follow-up to bug 822882 by
> treating unread as discussed on bug 800402.

Also see https://bugzilla.mozilla.org/show_bug.cgi?id=826071#c4 for related discussion.

Comment 12

[mlevin]

Issue reproduces on Inari with the following build:

Environmental  Variables:
Inari Build ID: 20130417070205
Kernel Date: Feb 21
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/6bac24e14538
Gaia: 2d048a9bdae54e4ec7d48326c2130591c8b869b6


Link to test case: https://moztrap.mozilla.org/manage/cases/?&pagenumber=1&pagesize=20&sortfield=created_on&sortdirection=desc&filter-id=2592&filter-productversion=82

Comment 13

[Jeni]

Issue repros on 

Issue repros in
Inari Build ID: 20130501070201
Kernel Date: Feb 21
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/010498e599a7
Gaia: 09046df332cd217cf4fad55c48ce9ce3f14ee5a4

And on

Unagi Build ID: 20130501070201
Kernel Date: Dec 5
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/010498e599a7
Gaia: 09046df332cd217cf4fad55c48ce9ce3f14ee5a4

There is no visual spot on email that shows how many unread messages you have.

Comment 14

[Andrew Sutherland [:asuth] (he/him)]

There's no need to keep adding comments that the bug isn't fixed on this bug or any bug where the bug status does not claim the bug is fixed.  If the bug does magically seem to be fixed, it is okay to comment then and suggesting close, though! :)

If there's a test-case for this bug, please disable it, especially since this is highly unlikely to ever reach v1.0.1 even if we do fix it.