Activity log for bug #1155679

Date Who What changed Old value New value Message
2013-03-15 16:13:03 Raphaël Valyi - http://www.akretion.com bug added bug
2013-03-16 01:34:59 MonExodus bug added subscriber MonExodus
2013-03-16 05:55:34 Erwin van der Ploeg (BAS Solutions) bug added subscriber Erwin van der Ploeg (Endian Solutions)
2013-03-16 15:02:47 Mario Arias bug added subscriber Mario Arias
2013-03-18 07:01:25 Amit Parik openobject-addons: status New Opinion
2013-03-18 23:21:59 Launchpad Janitor branch linked lp:~rvalyi/openobject-addons/crm-fixes-opportunity-regression-1155679
2013-03-19 10:55:13 Olivier Dony (Odoo) openobject-addons: status Opinion Invalid
2013-03-20 09:26:41 Jacques-Etienne Baudoux bug added subscriber Jacques-Etienne Baudoux
2013-03-23 18:52:09 Paulius Sladkevičius @ hbee bug added subscriber Paulius Sladkevičius
2013-04-06 20:25:58 Sergio Corato bug added subscriber Sergio Corato
2014-05-07 14:40:05 Carlos Lopez bug added subscriber Carlos Lopez
2014-08-11 22:42:47 Fabien (Open ERP) description Hello, How to reproduce ------------------------------- runbot + sale_crm module installed. Create a new prospect like this: subject: 'new project' company name: 'CompanyX' contact name: 'Joe' convert the lead it to an opportunity with the default settings (eg create new partner). By default the opportunity is related to the new contact Joe, who has been correctly created as a contact of CompanyX. But notice this is debatable whether it's good or not to link the opportunity to Joe instead of CompanyX. Indeed, CompanyX may have many contacts and this makes it hard to manage your opportunities by the companies behind the contacts. But there is worse: Now convert the opportunity to a new quote using default settings. By default: the new quote will be related to Joe, not CompanyX!! That is if you continue the flow, who will be invoiced will be Joe, not CompanyX, that is the accounting with CompanyX is going to be all wrong. Expected behavior ------------------------------- 1) at the very least, in such case, the default address/company for the quote conversion should be the parent CompanyX instead of contact Joe. 2) eventually, the opportunity could be related to CompanyX too instead of Joe. Eventually this could be an option and eventually the opportunity would be related to CompanyX but mentioning in some field the Joe contact. Hope to see this fixed. I think today the CRM acts as a "discover OpenERP" channel, it can not be that broken. And behavior was correct in 6.1 at least, so this is a regression and regressions aren't good. Hello, How to reproduce ------------------------------- <a href="https://odoo.com">Odoo New Website</a> [https://www.odoo.com|odoo] runbot + sale_crm module installed. Create a new prospect like this: subject: 'new project' company name: 'CompanyX' contact name: 'Joe' convert the lead it to an opportunity with the default settings (eg create new partner). By default the opportunity is related to the new contact Joe, who has been correctly created as a contact of CompanyX. But notice this is debatable whether it's good or not to link the opportunity to Joe instead of CompanyX. Indeed, CompanyX may have many contacts and this makes it hard to manage your opportunities by the companies behind the contacts. But there is worse: Now convert the opportunity to a new quote using default settings. By default: the new quote will be related to Joe, not CompanyX!! That is if you continue the flow, who will be invoiced will be Joe, not CompanyX, that is the accounting with CompanyX is going to be all wrong. Expected behavior ------------------------------- 1) at the very least, in such case, the default address/company for the quote conversion should be the parent CompanyX instead of contact Joe. 2) eventually, the opportunity could be related to CompanyX too instead of Joe. Eventually this could be an option and eventually the opportunity would be related to CompanyX but mentioning in some field the Joe contact. Hope to see this fixed. I think today the CRM acts as a "discover OpenERP" channel, it can not be that broken. And behavior was correct in 6.1 at least, so this is a regression and regressions aren't good.