Skip to content

[19.0][MIG] purchase_invoice_status_line: Migration to 19.0 - #3036

Open
BhaveshHeliconia wants to merge 19 commits into
OCA:19.0from
HeliconiaIO:19.0-mig-purchase_invoice_status_line
Open

[19.0][MIG] purchase_invoice_status_line: Migration to 19.0#3036
BhaveshHeliconia wants to merge 19 commits into
OCA:19.0from
HeliconiaIO:19.0-mig-purchase_invoice_status_line

Conversation

@BhaveshHeliconia

Copy link
Copy Markdown
Contributor

No description provided.

@OCA-git-bot OCA-git-bot added series:19.0 mod:purchase_invoice_status_line Module purchase_invoice_status_line labels Apr 28, 2026
@BhaveshHeliconia
BhaveshHeliconia force-pushed the 19.0-mig-purchase_invoice_status_line branch from 2d02475 to 75f9b02 Compare April 28, 2026 12:13
@BhaveshHeliconia
BhaveshHeliconia force-pushed the 19.0-mig-purchase_invoice_status_line branch 2 times, most recently from 61a3726 to 04bf2eb Compare August 10, 2026 12:27
JoanSForgeFlow and others added 18 commits August 10, 2026 18:00
Currently translated at 100.0% (9 of 9 strings)

Translation: purchase-workflow-18.0/purchase-workflow-18.0-purchase_invoice_status_line
Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-18-0/purchase-workflow-18-0-purchase_invoice_status_line/it/
Currently translated at 100.0% (12 of 12 strings)

Translation: purchase-workflow-18.0/purchase-workflow-18.0-purchase_invoice_status_line
Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-18-0/purchase-workflow-18-0-purchase_invoice_status_line/it/
@BhaveshHeliconia
BhaveshHeliconia force-pushed the 19.0-mig-purchase_invoice_status_line branch 3 times, most recently from 99150fb to 7b9e69b Compare August 11, 2026 04:08

@tonygalmiche tonygalmiche left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Tested on a local Odoo 19.0 instance:

  • Bug found: "Invoice Status" / "Force Invoiced" columns never appear on the
    actual Purchase Order form, only in the separate "Purchase Order Lines" menu
    (from purchase_order_line_menu). Root cause: the module only patches the
    reusable purchase.purchase_order_line_tree view, but the order lines list
    embedded in the PO form is defined inline in purchase.purchase_order_form
    and is not connected to that reusable view. The sibling module
    purchase_reception_status_line handles this correctly via an additional
    view (views/purchase_order.xml) that directly inherits
    purchase.purchase_order_form — purchase_invoice_status_line is missing the
    equivalent patch.

@BhaveshHeliconia
BhaveshHeliconia force-pushed the 19.0-mig-purchase_invoice_status_line branch from 7b9e69b to 9464da2 Compare August 17, 2026 07:48
@BhaveshHeliconia

Copy link
Copy Markdown
Contributor Author

Thanks @tonygalmiche! Added the view patch for purchase.purchase_order_form to include the columns in the embedded PO order lines list.

@BhaveshHeliconia
BhaveshHeliconia force-pushed the 19.0-mig-purchase_invoice_status_line branch from 9464da2 to 117292e Compare August 17, 2026 07:58
@BhaveshHeliconia
BhaveshHeliconia force-pushed the 19.0-mig-purchase_invoice_status_line branch from 117292e to 1f98db2 Compare August 17, 2026 08:06

@tonygalmiche tonygalmiche left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Tested on a local Odoo 19.0 instance:

  • "Invoice Status" / "Force Invoiced" columns now correctly display on the Purchase Order form (confirmed after the latest fix)
  • Line status correctly reflects billing progress (Nothing to Bill / Waiting Bills)

Thanks @BhaveshHeliconia for the quick fix on the missing view patch!

No further issues found. Works as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mod:purchase_invoice_status_line Module purchase_invoice_status_line series:19.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants