lp://staging/~partner-contact-core-editors/partner-contact-management/7.0
- Get this branch:
- bzr branch lp://staging/~partner-contact-core-editors/partner-contact-management/7.0
Branch merges
Related bugs
Related blueprints
Branch information
Recent revisions
- 42. By Holger Brunn (Therp)
-
[mrg] use _prepare_name from refactoring of partner_firstname
- 41. By David BEAL (ak)
-
[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
-
[IMP] partner_firstname: Make the function of the 'name' field inheritable.
- 39. By Leonardo Pistone
-
[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
-
[+] base_contact module
- 37. By Sandy Carter (http://www.savoirfairelinux.com)
-
Adapt user form to look like partner form
* Name field replaced by Firstname and Lastname - 36. By Joao Alfredo Gama Batista
-
[MRG][IMP] Adapt user form to display first name and last name like partner form
- 35. By Jonathan Nemry (Acsone)
-
[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 companyFor 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)
-
[ADD] Add passport and passport_partner modules: You can manage several passports for each contact.
- 33. By Sandy Carter (http://www.savoirfairelinux.com)
-
[FIX] base_location - Add context propagation to base_location
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)