Branch: 12.0

10.0

11.0

12.0

12.0_partner_gogocarto

12.3

14.0

14.0_partner_favorite

6.1

7.0

8.0

9.0

nj-12.0-partner_gogocarto_export_api

partner_gogocarto

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '12.0'

${ noResults }

Commit Graph

4 Commits (12.0)

Author	SHA1	Message	Date
Nikul-Chaudhary	c16d27cb60	[MIG] partner_second_lastname v11 to v12	5 years ago
Jon Zaballa	fe7edb4b51	11.0 partner_second_last_name required only if type = contact Description of the issue/feature this PR addresses: firstname, lastname and lastname2 fields should only be required if contact `type` is `contact`. In partner_firstname module this is done right with `('type', '=', 'contact')` leave in attrs required domain. But in partner_second_last_name there is no such leave, so if the contact is an address, the fields are mandatory too. Current behavior: Either firstname, lastname or lastname2 are mandatory when a contact is not a company. Desired behavior after PR is merged: firstname, lastname or lastname2 are mandatory when the contact is of type `contact`	5 years ago
Pedro M. Baeza	61d2a88177	partner_second_lastname: Migration to 10.0	7 years ago
Jairo Llopis	63f0ae38af	Add module partner_lastname2.	9 years ago