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

[17.0][MIG] purchase_order_line_sequence: Migration to 17.0 #2414

Open
wants to merge 36 commits into
base: 17.0
Choose a base branch
from

Conversation

StefanRijnhart
Copy link
Member

@StefanRijnhart StefanRijnhart commented Sep 23, 2024

From unmerged #1961
Depends on OCA/stock-logistics-workflow#1552

  • Set additional field context in get_field for compatibility with other modules
  • Refactor tests to use setUpClass

SerpentCS and others added 30 commits September 23, 2024 15:53
If the creation of purchase order lines is made with form view rather than tree view then the module misbehaves, ie, creates a line with sequence 9999. This fixes that without breaking the tree view usage. It also makes sure that the sequence is kept when duplicating a purchase order, which makes more sense. It seems that this was a typo/bug on the original module which was not manifestating when using tree view but becomes clear when allowing editing of the purchase order line with form view.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

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

Translation: purchase-workflow-12.0/purchase-workflow-12.0-purchase_order_line_sequence
Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-12-0/purchase-workflow-12-0-purchase_order_line_sequence/
Currently translated at 88.9% (8 of 9 strings)

Translation: purchase-workflow-12.0/purchase-workflow-12.0-purchase_order_line_sequence
Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-12-0/purchase-workflow-12-0-purchase_order_line_sequence/fr/
After odoo/odoo@49b143e

the sequence is correctly transmitted from purchase line to invoice line.
Currently translated at 100.0% (11 of 11 strings)

Translation: purchase-workflow-14.0/purchase-workflow-14.0-purchase_order_line_sequence
Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-14-0/purchase-workflow-14-0-purchase_order_line_sequence/es/
@StefanRijnhart StefanRijnhart added this to the 17.0 milestone Sep 23, 2024
@StefanRijnhart StefanRijnhart force-pushed the 17.0-mig-purchase_order_line_sequence branch 3 times, most recently from dd2c6da to 873d829 Compare September 23, 2024 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.