Created by Vincent Vinet on 2014-07-03 and last modified on 2014-07-03
Get this branch:
bzr branch lp:~savoirfairelinux-openerp/openobject-addons/7.0-bug-1168398-tta+afe+vv
Members of Savoir-faire Linux' OpenERP can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

Savoir-faire Linux' OpenERP

Recent revisions

9051. By Vincent Vinet on 2014-07-03

fix merge conflict

9050. By Vincent Vinet on 2014-07-03

[FIX] use the remaining quantity to split instead of original qty when splitting consume moves

9049. By Alexandre Fayolle - camptocamp on 2013-07-11

[MRG] merge back the fix on 7.0 head, and hopefully get green on runbot

9048. By Alexandre Fayolle - camptocamp on 2013-07-11

[IMP] fix typo in test, delete trailing whitespace, add an assertion

9047. By Alexandre Fayolle - camptocamp on 2013-07-11

[TEST] added test for bug lp:1168398

9046. By SnippetBucket.com on 2013-04-22

[FIX] bug:1168398/Incorrect behaviour when producing MO with component split in serial numbers.

9045. By Launchpad Translations on behalf of openerp on 2013-04-21

Launchpad automatic translations update.

9044. By Launchpad Translations on behalf of openerp on 2013-04-20

Launchpad automatic translations update.

9043. By Olivier Dony (Odoo) on 2013-04-20

[MERGE/ADD] Many important fixes for contact/company management + new module account_report_company

This patch comes with a corresponding server-side patch (revision 4946 revid: <email address hidden>)

- module-specific overrides of _commercial_fields() for all modules adding accounting/invoicing-related fields to res.partner

- corresponding changes to inherited views of res.partner form to hide these commercial fields when they are in fact "related fields" of their parent commercial entity. This mainly concerns 2 sections of the Partner form: the whole Accounting tab, and the bottom of the Sales&Purchase tabs with the pricelists and invoicing fields. These sections are replaced by a short message and a button to open the commercial entity to view/edit the fields

- a few fixes to properly delegate the resolution of various contact/address types to the corrected res.partner.address_get()

- changes to search views of the main business documents so that searching for a company name will also match its contacts

- a fix of the _find_accounting_partner() method that the account module uses to locate the partner to which journal entries must be linked - it will now use the same semantics as for "commercial entity"

- fix issue detected by Joël Grand-Guillaume in comment #34 of bug 1160365: when invoicing after delivery, the invoicing contact/address must be used rather than the main customer. Tests updated accordingly.

- add new 7.0 module "account_report_company": this module adds an extra stored field "commercial_partner_id" on Invoices to make reporting/aggregating by partner easier in the Invoice list and in the Invoice Analysis report. This module is expected to be merged in the main account module in the next major release. The module can be installed without any risk on any existing 7.0 databases.
This module also mitigates group_by issues on all models by adding a new stored function field `display_name` on res.partner that contains the name_get() result in the form "ACME, John Doe" and set it as the default _order for res.partner. This ensures that group_by entries for the same company will always be next to each other on all documents: "ACME" is directly followed by "ACME, John Doe", "ACME, John Anderson", etc. This field also replaces the `name` field in the list and kanban views of Partners, so that the display order matches the display labels.

- fixed unique constraints definition on some commercial fields on res.partner (l10n_ro)

9042. By Nicolas Vanhoren (OpenERP) on 2013-04-19

[FIX] pad: revert part of previous fix because it could produce problems in some cases

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.