lp:~jeffery9/ocb-addons/ocb-addons-fixups

Branch merges

Propose for merging

No branches dependent on this one.

Rejected for merging into lp:ocb-addons

Yannick Vaucher @ Camptocamp: Disapprove on 2014-04-02

Stefan Rijnhart (Opener): Disapprove on 2014-03-23

Pedro Manuel Baeza: Needs Information on 2013-11-08

Diff: 93 lines (+20/-5)

6 files modified

crm/crm_lead.py (+5/-1)
crm/crm_phonecall_view.xml (+3/-3)
crm/wizard/crm_lead_to_opportunity.py (+3/-0)
crm/wizard/crm_lead_to_opportunity_view.xml (+1/-1)
crm/wizard/crm_partner_binding.py (+7/-0)
crm/wizard/crm_phonecall_to_phonecall_view.xml (+1/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1208436: Lead to opportunity wizard: partner not created when existing partner found, even when choosing 'create' in the wizard	Low	Fix Released
Bug #1215829: phonecall scheduling from existing phonecall	Low	Confirmed
Bug #1247018: crm logged calls schedule another call in held state	Low	Confirmed

Link a bug report

Related blueprints

9648. By jeffery chen fan on 2013-11-08

merge with another fixups tree

9647. By jeffery chen fan on 2013-11-08

fix logical bugs in crm_lead2opportunity_partner and _lead_create_contact
that should not create dupcated partner

9646. By Launchpad Translations on behalf of openerp on 2013-11-07

Launchpad automatic translations update.

9645. By Launchpad Translations on behalf of openerp on 2013-11-06

Launchpad automatic translations update.

9644. By Nicolas Vanhoren (OpenERP) on 2013-11-05

[FIX] problem with pads, the demo configuration doesn't work if the server is using https. I simply changed the url for the demo version.

9643. By Olivier Dony (Odoo) on 2013-11-05

[FIX] sale,sale_stock: sales analysis view using incorrect JOIN and group by clause

Similarly to the recent fixes in Purchase Analysis,
the Sales Analysis view must not group on the quantity
field. It is one of the columns that must be aggregated,
not used to fold PO lines into the same
result row.
The line count was also incorrect because of this, and
had to be corrected to actually count() the underlying
SO lines.

In addition, the JOINs were done in the wrong order,
which could cause problems (e.g. if an empty SO ever
landed in the database, all the SO line columns
would be empty in the JOIN, and cause errors)

9642. By Olivier Dony (Odoo) on 2013-11-05

[FIX] purchase: analysis view must not group by quantity, otherwise identical PO lines are counted only once

The product quantity is one of the columns that must be
aggregated, not used to fold PO lines into the same
result row.
This, combined with missing aggregation operators
was causing multiple identical PO lines from the
same PO to be merged together and only counted once
in some aggregations.

9641. By Olivier Dony (Odoo) on 2013-11-04

[FIX] stock: no early currency rounding when computing average price

It is a common need to set a higher decimal precision
for `Product Price` (i.e. the product cost field) for
high volume / low value items. This may typically
require up to 4-6 decimals for e.g. EUR/USD-based
companies where the currency has 2 decimals.
In that case the product cost should be stored with
full precision without applying the currency rounding.
The appropriate currency rounding will be applied
anyway as soon as a transaction actually uses that
product cost (typically in a SO/PO)

9640. By Holger Brunn (Therp) on 2013-11-06

[FIX] resolve conflict between
http://bazaar.launchpad.net/~ocb/ocb-addons/7.0/revision/9584
and
http://bazaar.launchpad.net/~openerp/openobject-addons/7.0/revision/9564

9639. By Olivier Dony (Odoo) on 2013-11-04

[FIX] stock: `product cost` field in partial picking wizard must respect decimal precision

Without the right precision the default rounding is
applied and causes a possible loss of precision when
the `Product Price` precision is increased.
This can in turn lead to incorrect average price
computations.