Skip to content
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

[16.0][MIG] purchase_force_invoiced #1681

Merged
merged 26 commits into from
Feb 17, 2023

Conversation

alexis-via
Copy link
Contributor

2 small improvements:

  1. force_invoiced now has tracking=True (important !)
  2. force_invoiced in now invisible on RFQs

JordiBForgeFlow and others added 25 commits December 14, 2022 16:37
Currently translated at 100.0% (4 of 4 strings)

Translation: purchase-workflow-12.0/purchase-workflow-12.0-purchase_force_invoiced
Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-12-0/purchase-workflow-12-0-purchase_force_invoiced/zh_CN/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: purchase-workflow-13.0/purchase-workflow-13.0-purchase_force_invoiced
Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-13-0/purchase-workflow-13-0-purchase_force_invoiced/
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.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: purchase-workflow-15.0/purchase-workflow-15.0-purchase_force_invoiced
Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-15-0/purchase-workflow-15-0-purchase_force_invoiced/
@alexis-via
Copy link
Contributor Author

Tests are green, cool !

)
return product

def create_invoice_line(self, line, invoice):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like you can remove this method now.

Set force_invoiced field invisible on RFQs (state not in purchase or done)
force_invoiced is now tracked in chatter
Copy link
Contributor

@rousseldenis rousseldenis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review

@rousseldenis
Copy link
Contributor

@StefanRijnhart Could you update your review?

@StefanRijnhart
Copy link
Member

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 16.0-ocabot-merge-pr-1681-by-StefanRijnhart-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 12fac69 into OCA:16.0 Feb 17, 2023
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at f9db6fd. Thanks a lot for contributing to OCA. ❤️

@RodrigoBM
Copy link
Contributor

next time link to migration issue please #1585

@StefanRijnhart
Copy link
Member

/ocabot migration purchase_force_invoiced

@OCA-git-bot OCA-git-bot added this to the 16.0 milestone Feb 17, 2023
@OCA-git-bot OCA-git-bot mentioned this pull request Feb 17, 2023
52 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.