-
-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[15.0][MIG] stock_picking_report_valued #181
[15.0][MIG] stock_picking_report_valued #181
Conversation
For avoiding problems if you don't have access to sales orders (stricter warehouse users, inter-company records...).
- This commit odoo/odoo@41bea41 breaked the inheritance.
In certain conditions of the DB (i.e. integration tests), previous code doesn't assure the price is going to be 100.
[FIX] stock_picking_report_valued: Wrong taxes amount if round globally (OCA#56) [FIX] stock_picking_report_valued: Remove round_method condition because don't apply here [FIX] stock_picking_report_valued: price_reduce is stored with product decimal precision [FIX] stock_picking_report_valued: division_by_zero when unrelated sale order [FIX] stock_picking_report_valued: Improve code [FIX] stock_picking_report_valued: Multiple taxes in sale line (WIP)
Hey @flachica, thank you for your Pull Request. It looks like some users haven't signed our Contributor License Agreement, yet.
Appreciation of efforts, |
Currently translated at 76.9% (20 of 26 strings) Translation: stock-logistics-reporting-14.0/stock-logistics-reporting-14.0-stock_picking_report_valued Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-reporting-14-0/stock-logistics-reporting-14-0-stock_picking_report_valued/fr_FR/
0981494
to
4fe1286
Compare
/ocabot migration stock_picking_report_valued |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I never liked that tax column order in valued_report_picking header but anyway.... LGTM
This PR has the |
@flachica please rename latest commit message to follow standard guidelines: |
4fe1286
to
c45ef8b
Compare
Sorry. Message was fixed, thanks for your review @pedrobaeza |
I'm afraid it's still not correct. Please read the link I have put, although as tip it should be something like: |
c45ef8b
to
51cca07
Compare
Done @pedrobaeza |
Why do you insist with |
I'm merging now as not being critical and don't block this, but please follow strictly guidelines (or didn't you read them?) /ocabot merge nobump |
On my way to merge this fine PR! |
Congratulations, your PR was merged at ac93374. Thanks a lot for contributing to OCA. ❤️ |
In the guideline I read "Use tags as listed in the Odoo Guidelines with the following extensions: - [MIG] for migrating a module" I haven't found anything about how to name the version. And yes, I have seen that the tag issue was included last year. When someone tells me to read something interesting I do it. |
I find this one referred from OCA guidelines to be very instructive: Anyways, it's true that the document contains several incorrect things that I'm fixing in OCA/odoo-community.org#68 |
No description provided.