Skip to content

[19.0][MIG] stock_request_partner: Migration to 19.0#5

Open
alan196 wants to merge 12 commits into
Jarsa:19.0from
Jarsa-dev:19.0-mig-stock_request_partner
Open

[19.0][MIG] stock_request_partner: Migration to 19.0#5
alan196 wants to merge 12 commits into
Jarsa:19.0from
Jarsa-dev:19.0-mig-stock_request_partner

Conversation

@alan196

@alan196 alan196 commented Jul 12, 2026

Copy link
Copy Markdown

Migration of stock_request_partner to 19.0. Same content as OCA#99.

Changes for 19.0:

  • Adapt _prepare_procurement_values override: procurement.group was replaced by stock.reference in core, so the partner is now passed directly in the procurement values and propagated to the picking.
  • Views: treelist, update stock_request_ids context to match the 19.0 base view (default_reference_ids, default_route_id) plus default_partner_id.
  • Tests: migrate to setUpClass, create partners instead of relying on demo data, use a shared stock.reference for the multi-line order test and assert the partner on the resulting picking.
  • Use self.env._() and remove the old 17.0 migration script.

@jarsabot

Copy link
Copy Markdown
    **WARNING**: Could not link to Odoo task. Record ID not found in the title of the MR, supported formats:
{ record type }#{ number }

Available types: 'task#', 't#' (case insensitive)

Examples:

  • task#123

  • i#123

@codecov-commenter

Copy link
Copy Markdown

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

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.

6 participants