lp:~openerp-dev/openobject-addons/6.1-opw-575213-skh

Branch merges

Propose for merging

No branches dependent on this one.

Approved for merging into lp:openobject-addons/6.1

Naresh(OpenERP): Pending requested 2012-05-28

Diff: 12 lines (+1/-1)

1 file modified

crm_claim/crm_claim_view.xml (+1/-1)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

6816. By Somesh Khare on 2012-05-28

[FIX] Crm Claim:Inconsistency in process of setting Stage in a claim(Case: Ref 575213)

6815. By Launchpad Translations on behalf of openerp on 2012-05-28

Launchpad automatic translations update.

6814. By Launchpad Translations on behalf of openerp on 2012-05-27

Launchpad automatic translations update.

6813. By Launchpad Translations on behalf of openerp on 2012-05-26

Launchpad automatic translations update.

6812. By Xavier ALT on 2012-05-25

[MERGE] OPW 574991: rml reports: move setLang() before <pto_header/> otherwise it won't be correctly translated

6811. By Launchpad Translations on behalf of openerp on 2012-05-25

Launchpad automatic translations update.

6810. By Launchpad Translations on behalf of openerp on 2012-05-24

Launchpad automatic translations update.

6809. By Xavier ALT on 2012-05-24

[MERGE] OPW 575004: stock: fix font for product name/variant in packaging report

6808. By Xavier ALT on 2012-05-24

[MERGE] crm_partner_assign: test: be more lenient about partner localisation

    As of today, google maps tend to localize:
       Avenue de la Liberté 56, 1000 Brussels, , Belgium
    As:
       Place de la Liberté 56, 1000 Bruxelles, Belgique

    making imprecision and failing geolocalizaton test of
    'crm.crm_case_abcfuelcounits0' (current modification is backported from
    trunk unit-test)

6807. By Olivier Dony (Odoo) on 2012-05-23

[FIX] decimal_precision: properly invalidate cache when changing precisions

This was working previously because the cache was disabled,
due to bug #988743. Now that the cache is working again,
it needs to be properly invalidated whenever a decimal.precision
record is created or deleted, otherwise all computations
will use an incorrect precision.