1080879 - When adding/editing a contact, a name shouldn't be required

Status: RESOLVED WONTFIX

(Hello (Loop) :: Client, defect, P4)

Description

[Matthew N. [:MattN]]

I should be able to add just an email address and have it displayed in the list with it. Many contact applications I have used work this way and it speeds up the flow to call a new contact.

Darrin, what do you think?

Comment 1

[Darrin Henein [:darrin]]

I'm not against this -- we would just need to modify the contacts list UI as well to better support nameless contacts.

Comment 2

[:shell escalante]

sevaan - as you are redoing the design, what do you think of this.  you can ask RT.  low priority

Comment 3

[Sevaan Franks [:sevaan]]

I think it is a fine idea. If no name is entered, we can create the contact and populate the Name field with the email address. Next time they edit the contact, the email will be in the name field as well for them to edit.

In the panel it would look like this: http://cl.ly/image/323i1q0C1Y12

Comment 4

[:shell escalante]

Can you update the design on bug 1099950... just so that after email is entered the button goes green - but the name and phone are optional. (we were going to requiring name and email before making "add contact" green - but sounds like only will require contact).

Comment 5

[Sevaan Franks [:sevaan]]

Done: https://bugzilla.mozilla.org/attachment.cgi?id=8562969

Comment 6

[Matthew N. [:MattN]]

(In reply to Sevaan Franks [:sevaan] from comment #3)
> I think it is a fine idea. If no name is entered, we can create the contact
> and populate the Name field with the email address. Next time they edit the
> contact, the email will be in the name field as well for them to edit.

Why bother duplicating the contact information in the name field? That just puts it in the way the next time the user wants to assign a name. i.e. why not just have the list code fallback to the email address/phone number instead of actually saving those values in the name field?

Comment 7

[Sevaan Franks [:sevaan]]

(In reply to Matthew N. [:MattN] from comment #6)
> Why bother duplicating the contact information in the name field? That just
> puts it in the way the next time the user wants to assign a name. i.e. why
> not just have the list code fallback to the email address/phone number
> instead of actually saving those values in the name field?

My thinking was that it would be the impetus on the user to edit the contact and give it a name. Like, "You don't want to give this contact a name? Okay, we will." But your solution works as long as this is propagated everywhere in the UI (i.e. if an incoming call from a contact comes in, and they don't have a name, the email is displayed.

https://bugzilla.mozilla.org/attachment.cgi?id=8563000

Comment 8

[Mark Banner (:standard8)]

We are currently reworking the Loop "user journey" (bug 1209713) and as part of this direct calls and contacts are being removed. Therefore closing contact related bugs as wontfix.

Tracking id: contactuserjourneyclosing