Syncing from upstream OCA/purchase-workflow (18.0) #1692
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-Authored-By: Eric @ Elico Corp <[email protected]>
The purchase BI analysis is not taking into account the "Force invoiced" check for showing their quantity to be billed, so it gives contradictory information from the search filter and the pivot. This commit adapts the SQL report for taking this into account.
…with inconsistent data
Set force_invoiced field invisible on RFQs (state not in purchase or done) force_invoiced is now tracked in chatter
- Switch to setUpClass for avoiding repeat the same setup for each test. - Include context keys for avoiding mail operations overhead.
Currently translated at 100.0% (4 of 4 strings) Translation: purchase-workflow-17.0/purchase-workflow-17.0-purchase_force_invoiced Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-17-0/purchase-workflow-17-0-purchase_force_invoiced/it/
* Reset qty_to_invoice on lines of force invoiced orders * Adapt SQL report override to the use of odoo.tools.sql.SQL Co-authored-by: Stefan Rijnhart <[email protected]>
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: purchase-workflow-18.0/purchase-workflow-18.0-purchase_force_invoiced Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-18-0/purchase-workflow-18-0-purchase_force_invoiced/
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 18.0 #1692 +/- ##
==========================================
+ Coverage 95.66% 95.75% +0.09%
==========================================
Files 133 141 +8
Lines 3298 3393 +95
Branches 297 300 +3
==========================================
+ Hits 3155 3249 +94
- Misses 69 70 +1
Partials 74 74 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
bt_gitbot