lp:~partner-contact-core-editors/partner-contact-management/7.0

Branch merges

Propose for merging

14 branches proposed for merging into this one.

No branches dependent on this one.

Related source package recipes

1 recipe using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

42. By Holger Brunn (Therp) on 2014-07-17

[mrg] use _prepare_name from refactoring of partner_firstname

Merged branch lp:~therp-nl/partner-contact-management/7.0-firstname_display_name_trigger_prepare_name

41. By David BEAL (ak) on 2014-07-12

[ADD] base_partner_help: Module for additional methods for manage partner. For now, there is a method to deal with addresses (get_split_address).

Merged branch lp:~akretion-team/partner-contact-management/7.0-partner-helper-dbl

40. By Alexis de Lattre on 2014-06-11

[IMP] partner_firstname: Make the function of the 'name' field inheritable.

Merged branch lp:~akretion-team/partner-contact-management/partner-firstname-inheritable

39. By Leonardo Pistone on 2014-05-16

[mrg] Add module base_partner_merge backport from trunk
Add module account_partner_merge needed to fix merging when account is installed

Merged branch lp:~camptocamp/partner-contact-management/add-base_partner_merge

38. By Xavier ALT on 2014-04-30

[+] base_contact module

Merged branch lp:~savoirfairelinux-openerp/partner-contact-management/partner-contact-management-base_contact

37. By Sandy Carter (http://www.savoirfairelinux.com) on 2014-03-21

Adapt user form to look like partner form
* Name field replaced by Firstname and Lastname

36. By Joao Alfredo Gama Batista on 2014-03-21

[MRG][IMP] Adapt user form to display first name and last name like partner form

Merged branch lp:~savoirfairelinux-openerp/partner-contact-management/user-firstname

35. By Jonathan Nemry (Acsone) on 2014-03-12

[MRG]

For Partner:

1) Create always the SQL constraint on 'lastname'
2) Better implementation of "_write_name" allowing more intuitive update of the partner name when processing from another model (ex: res_user), i.e., try to keep the firstname if unchanged
3) When duplicating a partner, avoid to repeat the firstname in the name
4) Beautify the inner form for children contacts (placing fields as in the main form)
5) Allow edition of the field name in the inner form if child is a company

For User:

1) Reintegrate the name as "required"
2) When duplicating a user, avoid to repeat the firstname in the related partner name

Merged branch lp:~acsone-openerp/partner-contact-management/7.0-partner-firstname

34. By El Hadji Dem (http://www.savoirfairelinux.com) on 2014-03-04

[ADD] Add passport and passport_partner modules: You can manage several passports for each contact.

Merged branch lp:~savoirfairelinux-openerp/partner-contact-management/partner-contact-management-base_contact_add_passport_passport_partner

33. By Sandy Carter (http://www.savoirfairelinux.com) on 2014-02-24

[FIX] base_location - Add context propagation to base_location

Merged branch lp:~savoirfairelinux-openerp/partner-contact-management/1279118

Bug #1279118: name get of base_location does not translate county