lp:~nemry/partner-contact-management/7.0-8.0-compatibility

Created by Jonathan Nemry (Acsone) on 2014-08-04 and last modified on 2014-08-04
Get this branch:
bzr branch lp:~nemry/partner-contact-management/7.0-8.0-compatibility
Only Jonathan Nemry (Acsone) can upload to this branch. If you are Jonathan Nemry (Acsone) please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Jonathan Nemry (Acsone)
Project:
Partner and Contact Management
Status:
Development

Recent revisions

43. By Jonathan Nemry (Acsone) on 2014-08-04

[CHG] change import to be odoo compliant and to avoid bad import error under v80

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

[mrg] use _prepare_name from refactoring of partner_firstname

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).

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

[IMP] partner_firstname: Make the function of the 'name' field 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

38. By Xavier ALT on 2014-04-30

[+] base_contact module

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

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

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.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:~partner-contact-core-editors/partner-contact-management/7.0
This branch contains Public information 
Everyone can see this information.