Ticket #1332930 (new Feature Requests: None)

Opened 3 years ago

Last modified 6 months ago

Addressbook - Extra Contacts details

Reported by: nobody Owned by: nobody
Priority: 5 Milestone: 0.2-beta
Component: Other Version: None
Severity: normal Keywords:
Cc:

Description (last modified by thomasb) (diff)

Ability to add extra information against a Contact. Phone, mobile and possibly Address would be handy. Standard stuff, but handy when out on the road.

Change History

Changed 3 years ago by jsaathof

Logged In: YES 
user_id=367201

Multiple email addresses would be nice too.

Changed 3 years ago by nobody

Logged In: NO 

Perhaps one thing you can do is simply add a space similar to this add a 
comment box, where people can add additional info, notes, etc.  That way, you 
are not limiting yourself to whatever fields are available.  This is pretty standard 
stuff so hopefully when the stable release comes out, the feature will be there.  
Also, perhaps you can add an import from Outlook feature or import from cvs 
file support.... would be nice to bring all those contacts in that have been 
collected over time.

Changed 3 years ago by mawiseman

Logged In: YES 
user_id=1250651

Multiple email addresses is high on my list

Changed 2 years ago by thomasb

  • status changed from assigned to new
  • severity changed from critical to normal
  • description modified (diff)
  • milestone deleted

Changed 10 months ago by trappist

A brief look at the code suggests this would take a bit of work, but the *right* way to do this would involve a series of additional tables, for anything a contact can have more than one of, like phone numbers and email addresses. So you'd have an email_addresses table with email_id, user_id and contact_id (plus any management columns like del). A phone_numbers table would be similar but might also have a type column to specify home, office, cell, etc.

If we want to do addresses, there'd be a similar table for these, but they wouldn't have a contact_id since contacts and addresses can have a many-to-many relationship, so you'd need a join table like contacts_addresses with just a contact_id and an address_id.

While I'm at it, preferences should have their own table too instead of being serialized in the users table.

Changed 6 months ago by seansan

  • summary changed from Extra Contacts details to Addressbook - Extra Contacts details
  • milestone set to 0.2-beta

Adressbook - 0.2 beta

Changed 6 months ago by seansan

Also see #1484603

Note: See TracTickets for help on using tickets.