Closed
Bug 808650
Opened 13 years ago
Closed 13 years ago
[email] contact list do not distinguish between contacts with email and without
Categories
(Firefox OS Graveyard :: Gaia::E-Mail, defect)
Tracking
(b2g18+ fixed, b2g18-v1.0.1 fixed)
RESOLVED
FIXED
People
(Reporter: pabloUX, Assigned: kgrandon)
Details
(Whiteboard: interaction UX-P1, [TEF_REQ], PRODUCT-FEATURE)
Attachments
(1 file)
|
223 bytes,
text/html
|
asuth
:
review+
vingtetun
:
approval-gaia-v1+
|
Details |
currently, contact list when you are adding e-mail recipents is complete, so If you want to add an email you should try in order to know if the email info is added to the contact details.
| Reporter | ||
Updated•13 years ago
|
Severity: critical → normal
Priority: -- → P2
Whiteboard: Interaction design
Contacts without emails should not show up in contacts selection list if there is no email address associated with the contact.
Updated•13 years ago
|
Priority: P2 → --
Whiteboard: Interaction design → interaction, UX-P2
| Assignee | ||
Comment 3•13 years ago
|
||
Appears to only be a problem with the contacts app, and the fix doesn't seem to be too difficult. I'll take a stab as this has sat for a few months now...
Assignee: nobody → kgrandon
Flags: needinfo?(bugmail)
| Assignee | ||
Updated•13 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Assignee | ||
Comment 4•13 years ago
|
||
Pull request to filter for contacts with email addresses.
Attachment #703303 -
Flags: review?
| Assignee | ||
Comment 5•13 years ago
|
||
Comment on attachment 703303 [details]
Github pull request pointer
Looking for a review here if possible, thanks!
Attachment #703303 -
Flags: review? → review?(jmcf)
Comment 6•13 years ago
|
||
[TEF_REQ] as Feature required for TEF build.
Whiteboard: interaction, UX-P2 → interaction UX-P1, [TEF_REQ]
Updated•13 years ago
|
Whiteboard: interaction UX-P1, [TEF_REQ] → interaction UX-P1, [TEF_REQ], PRODUCT-FEATURE
Comment 7•13 years ago
|
||
Comment on attachment 703303 [details]
Github pull request pointer
It's been 2 weeks and I'm technically a peer of gaia and this seems like a very small/straightforward patch, so r=asuth.
Attachment #703303 -
Flags: review?(jmcf) → review+
| Assignee | ||
Comment 8•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 9•13 years ago
|
||
This has a fix and is a TEF_REQ; can we land this on v1.0.0 and/or v1-train?
blocking-b2g: --- → tef?
Comment 10•13 years ago
|
||
(In reply to Andrew Sutherland (:asuth) from comment #9)
> This has a fix and is a TEF_REQ; can we land this on v1.0.0 and/or v1-train?
Andrew, I think this is not a blocker as this would not block the release. However, I'd suggest you request directly gaia-approval (and tracking-b2g18 if you want). Given how small the change is and the low risk it has I think it is highly likely triagers accept this to go to v1-train.
Updated•13 years ago
|
blocking-b2g: tef? → ---
Comment 11•13 years ago
|
||
Comment on attachment 703303 [details]
Github pull request pointer
[Approval Request Comment]
Bug caused by (feature/regressing bug #):
User impact if declined: Contact list will show contacts in the address book without e-mail addresses. We think this would be great on v1.0.0 too since it's TEF_REQ.
Testing completed: Kevin!
Risk to taking this patch (and alternatives if risky): Not believed risky, patch is tiny.
Attachment #703303 -
Flags: approval-gaia-v1?(21)
Updated•13 years ago
|
tracking-b2g18:
--- → ?
Comment 12•13 years ago
|
||
Comment on attachment 703303 [details]
Github pull request pointer
Sounds good to me but I believe you need to have a tef+ approval to land on 1.0.0. Is that what you're trying to achieve?
Attachment #703303 -
Flags: approval-gaia-v1?(21) → approval-gaia-v1+
Comment 13•13 years ago
|
||
For Telefónica, landing it in v1-train is enough.
Comment 14•13 years ago
|
||
v1-train: baf2dcafc5d14f532459fb7c8c59e6f8f1ac6712
status-b2g18:
--- → fixed
Updated•13 years ago
|
Comment 15•13 years ago
|
||
Batch edit: bugs fixed on b2g18 since 1/25 branch of v1.0 are fixed on v1.0.1
status-b2g18-v1.0.1:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•