919004 - [1.2][email] Notifications UI does not differentiate clearly between emails received in multiple email accounts configured

Status: RESOLVED WORKSFORME

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

Description

[Parul Mathur]

Test Environment:
Device: Leo
OS version: 1.2.0.0-prerelease
Firmware revision: D300f10a
Hardware revision: d300
Platform version: 26.0a2
Gecko: 0322470077b7
Build Identifier: 20130920004004
Update channel: leo/1.2.0/nightly
Gaia: 2e88444c39998e0b90513ad9f8ab9413f3fe246f1379486243
Git commit info: 2013-09-20 02:00:38

Steps to reproduce:
1. Go to Settings > Display and set Screen timeout to 1 minute.
2. On the home screen, tap on the E-Mail icon to launch the email app. 
3. Setup 2 or more new email accounts or ensure that they are already configured with the following options:
   A. Check for new messages: Every 5 minutes
   B. Display notifications for new messages: ON 
4. Press the home button to send the email app in the background. 
5. Allow the phone screen to time out through inactivity.
6. On a computer, sign in to the configured email accounts and arrange to receive several emails in them. (This can be done either by sending emails from another account or by subscribing to a high-volume mailing list.)  

Expected Results: 
After the email app sync with both the mail servers, it should generate a notification of new email received for both the accounts on the phone lock screen as well as the Utility Tray. The notifications should make it clear which emails have been received in which email accounts.

Actual Results: 
After the email app syncs with the mail server, it generates a notification of new email received on the phone lock screen as well as the Utility Tray. The different email accounts are not clearly distinguished; it is not possible to tell which email was received in which account.
(see screenshot https://bug916516.bugzilla.mozilla.org/attachment.cgi?id=804976)

Comment 1

[Dylan Oliver [:doliver]]

triage: blocking, bug in new feature for 1.2

Comment 2

[James Burke [:jrburke]]

Asking for UX guidance: from the meeting, we talked about some options, none were obvious winners, and Rob wanted to think more about it. Recap for Rob:

For single email notifications, the sender and subject can be so long as to make it unclear which account generated the notification (the referenced screen shot). Some things talked about:

* Putting the target email account before the subject, which practically would mean not seeing much of the subject.
* Just always use the "X New Emails - [email account]", where in this case it would be "1 New Email - [email account]".
* Like previous, but maybe use the other line of text to show "Sender - Subject", but knowing that subject will often be truncated/hidden by ellipses to be super useful.

Comment 3

[Stephany Wilkes]

Flagging Rob and Jacqueline on this email question.

Comment 4

[Rob MacDonald [:robmac]]

Hi James - Sorry for the delay. I've put together a couple of options but would like to discuss them with you if you're available. I'll track you down on Wednesday afternoon. - Rob

Comment 5

[James Burke [:jrburke]]

Just talked to Rob in person. Summary of what is desired:

# With one email account configured:

## Notification for one message synced:

Email Subject
Sender

## Notification for more than one message synced:

N New Emails
Sender 1, Sender 2, Sender 3

# With multiple email accounts configured:

## Notification for one message synced:

1 New Email ([e-mail])
Sender "Email Subject"

## Notification for more than one message synced:

N New Emails ([e-mail])
Sender 1, Sender 2, Sender 3

Note: these changes mean there are some localization-related changes -- the parentheses around target account, and the usage of quotes around the "Email Subject" case.

Comment 6

[Evan Tseng [:evanxd]]

The PR in bug 918998 also fix this bug(919004).

Comment 7

[Evan Tseng [:evanxd]]

master: https://github.com/mozilla-b2g/gaia/commit/0bbb26644f47f9ad6680136a122b0289cb2e183e

Comment 8

[James Burke [:jrburke]]

Marking as WORKSFORME instead of fixed, so that the branch updating and l10n tracking is a bit clearer -- just the changeset in bug 918998 is needed, and this bug is fixed as part of that changeset.

Comment 9

[Evan Tseng [:evanxd]]

Hi James,
Got it. Thanks.