Merge lp:~therp-nl/openobject-addons/7.0-lp1168948-set_tax_code_sequence_from_template into lp:openobject-addons/7.0
Proposed by
Stefan Rijnhart (Opener)
Status: | Rejected |
---|---|
Rejected by: | Martin Trigaux (OpenERP) |
Proposed branch: | lp:~therp-nl/openobject-addons/7.0-lp1168948-set_tax_code_sequence_from_template |
Merge into: | lp:openobject-addons/7.0 |
Diff against target: |
23 lines (+6/-0) 1 file modified
account/account.py (+6/-0) |
To merge this branch: | bzr merge lp:~therp-nl/openobject-addons/7.0-lp1168948-set_tax_code_sequence_from_template |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Stéphane Bidoul (Acsone) (community) | Approve | ||
Martin Trigaux (OpenERP) (community) | Disapprove | ||
Fabien (Open ERP) | Needs Information | ||
Review via email: mp+158816@code.launchpad.net |
To post a comment you must log in.
Unmerged revisions
- 9013. By Stefan Rijnhart (Opener)
-
[FIX] Set tax code sequence from template
I have the feeling that it's simpler to have only one field (code and not sequence), but I do not know all the countries. So, the right merge would be to remove 'sequence' and keep the order by "code".
But I am not sure about this as I don't know all the countries.
To decide on the best approach, we should review account.tax.code structure of existing l10n_... modules to check if there are an example where it's worth having a sequence that does not satisfy the "order by code".
But, for sure, there is a bug, because 1/ order used in reports should come from templates (that was the intent of your fix I guess) and 2/ it's not normal to have a specific order in the report and another one in the screen (_order) which is impossible to understand for a end-user perspective.