Migration to version 18.0

Open
#2,425 48 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend

Research direction

Read the OCA migration guide linked in the issue and choose an unchecked module from the migration list. Check that module’s migration requirements and current code, then migrate it for version 18.0 and follow the repository’s contribution process. Done means the module is migrated and its checklist entry is marked complete; several modules already have linked pull requests.

Written by the indexing model from the issue text.

Description

help wanted no stale work in progress

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0

Modules to migrate

  • procurement_purchase_no_grouping
  • procurement_purchase_sale_no_grouping - By @Andrii9090-tecnativa - #2952
  • product_supplierinfo_purchase_contact - By @victoralmau - #2745
  • purchase_advance_payment
  • purchase_all_shipments - By @lef-adhoc - #2472
  • purchase_allowed_product - By @Robrechtc - #2684
  • purchase_analytic_global - By @yankinmax - #2558
  • purchase_blanket_order
  • purchase_cancel_order - By @HeliconiaSolutions - #2484
  • purchase_cancel_reason
  • purchase_commercial_partner - By @StefanRijnhart - #2438
  • purchase_delivery_split_date
  • purchase_deposit - By @lef-adhoc - #2468
  • purchase_exception - By @yankinmax - #2506
  • purchase_force_invoiced - By @StefanRijnhart - #2585
  • purchase_invoice_method
  • purchase_invoice_plan
  • purchase_last_price_info - By @StefanRijnhart - #2439
  • purchase_line_reassign - By @eduezerouali-tecnativa - #2794
  • purchase_lot - By @BT-jcolmeiro - #2715
  • purchase_no_rfq
  • purchase_open_qty - By @StefanRijnhart - #2431
  • purchase_order_archive - By @HeliconiaSolutions - #2495
  • purchase_order_line_menu - By @StefanRijnhart - #2430
  • purchase_order_line_sequence - By @AEstLo - #2709
  • purchase_order_no_zero_price - By @Anxo82 - #3138
  • purchase_order_product_recommendation - By @pilarvargas-tecnativa - #2730
  • purchase_order_product_recommendation_brand - By @pilarvargas-tecnativa - #2884
  • purchase_order_product_recommendation_xlsx - By @Anxo82 - #2929
  • purchase_order_qty_change_no_recompute - By @antonioburic - #2524
  • purchase_order_supplier_return - By @Vicent-S73 - #2871
  • purchase_order_supplierinfo_update - By @ghost - #2500
  • purchase_order_type - By @StefanRijnhart - #2437
  • purchase_order_type_dashboard
  • purchase_order_uninvoiced_amount - By @juancarlosonate-tecnativa - #2548
  • purchase_packaging_default - By @YassineTal - #2587
  • purchase_partner_incoterm - By @LucasTran380381 - #2445
  • purchase_partner_selectable_option - By @juancarlosonate-tecnativa - #2594
  • purchase_reception_notify
  • purchase_reception_status - By @astirpe - #2501
  • purchase_request
  • purchase_request_tier_validation
  • purchase_request_type - By @victoralmau - #2625
  • purchase_requisition_tier_validation - By @StefanRijnhart - #2939
  • purchase_sale_link_by_origin
  • purchase_security
  • purchase_sign - By @Anushapadinharepurakkal - #2665
  • purchase_stock_price_unit_sync - By @ThiagoMForgeFlow - #2518
  • purchase_tag
  • purchase_tier_validation - By @Quan-nhm - #2447
  • purchase_triple_discount - By @Borruso - #2596
  • purchase_warn_message
  • purchase_warn_option - By @sabrinaRMartin - #2921
  • sale_purchase_force_vendor - By @jaydeep32 - #2523
  • stock_move_purchase_price_update - By @eduezerouali-tecnativa - #2805
  • supplier_calendar

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

Dominant language
HTML
Stars
294
Forks
995
Avg merge
5d 8h
Merged PRs (30d)
16

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OCA/purchase-workflow

All issues in OCA/purchase-workflow

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.