Daily updates from Odoo
Navigate
Branch
Tuesday, June 11, 2019
26 changes
New functionality added to Odoo
This pull request adds a new way to view forecasted inventory across products in one place, making stock planning easier. It also includes consistency fixes for expenses, accounting, sales margins, demo data, and web communication/security cleanup.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change lays the groundwork for displaying partner records on a map by making location coordinates available more broadly. It also adjusts website editor styling and documentation so the new map view can work consistently across relevant screens.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Adds a map-based view so users can see contacts, stock pickings, and project tasks as location markers. This helps teams visualize where work, deliveries, or contacts are located and can show routes when Mapbox is configured.
Enhancements to existing features
CRM now estimates lead success probability automatically using past won and lost leads instead of relying only on sales stages. This gives sales teams more data-driven prioritization while still allowing users to manually override a lead's probability when needed.
Original PR description
This merge replaces the stage based probability on leads by a new Predictive Lead scoring mechanism based on Naive Bayes Probability computation theorem. Probability are now computed automatically based on past experience (already lost and won leads) and based on multiple criteria (field values on leads). The user is still able to set a probability on a lead manually, or come back to a automated probability, both via the lead form. A cron runs every day to rebuild the frequency table and to recompute all the active pending leads. See sub commits for more details. Special thanks to @awa-odoo who did his job. Quite well indeed! Special thanks to @tbe-odoo who helped me for testing and performance optimisation. Task ID : 1925439 NOTE : This task must be followed by task ID 2008365 : Remove old lead scoring system
Odoo now shows a clear warning icon and tooltip when a user has not set their timezone in preferences. This helps users notice and correct missing timezone settings, reducing confusion around dates, times, and scheduling.
Original PR description
- Icon displayed next to preferences if user haven't set timezone - same icon next to the timezone field - added relevant tooltip Task:https://www.odoo.com/web#id=1916132&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad:https://pad.odoo.com/p/r.6e47aeee8e490bd75f98109897af68c1 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website debug pages will now receive standard updates when the website module is upgraded, as long as they have not been manually changed. This helps keep multi-website setups aligned with improvements and avoids outdated page structures.
Original PR description
Before this commit, those pages would be flag as noupdate. If not modified, those view would not get modification on module update, which is not logic. Now, those view will benefit from any update. It makes even more sense since multi-website, as those views will never get modified directly (it will COW).
The Bill of Materials Structure report now shows products and quantities without displaying costs, making it safer to share with customers or other third parties. Cost details remain available in the dedicated Structure and Cost report, while the redundant BoM Cost report is removed.
Original PR description
The BoM Structure report should only list the products and quantity but no their cost because sometimes shared with customers Task : https://www.odoo.com/web#id=1969709&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.3298fe37c3e5f135a45a8b6919299575 Task ID - 1969709 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adjusts an internal test for the website product comparison feature to use a standard tour-starting helper. It helps keep automated checks consistent and easier to maintain, with no expected change for shoppers or website managers.
Original PR description
Oversight of forward port.
The CRM now supports predictive lead scoring with clearer handling of sales probabilities and won or lost stages. This helps sales teams better prioritize opportunities and manage pipeline outcomes with more accurate guidance.
Purchase order cancellations now follow warehouse and manufacturing rules more accurately, cancelling only the related stock movements that should be stopped. This helps prevent unintended downstream cancellations after goods have reached stock or later production stages.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website CRM scoring app now aligns with the newer predictive lead scoring approach, using lead data and won-stage signals instead of fixed probabilities tied to sales stages. This should make opportunity scoring more data-driven and adaptable, while also adding language as an optional factor in scoring calculations.
Original PR description
This merge is the continuity of Community PR #33589 and adapt the website_crm_sroce module to work with the new PLS mechanism. See sub commit for more details. Task ID : 1925439 NOTE : This task must be followed by task ID 2008365 : Remove old lead scoring system
Field service teams get a clearer end-to-end task flow covering time tracking, validation, invoicing, worksheet reporting, and sales order handling. The update also improves access roles, onboarding, demo data, and automatically handles stock moves for materials used from field service tasks.
Original PR description
This merge contains many commits with different goals. Some are purely technical: - cleaning code - do some technical renaming - move some code parts Some provides functionnal features: - auto validation of stock moves when creating a sales order from a FSM task - ability to set the timesheet timer in "pause" state - allow user to print and send worksheet report (custom report, form view converted into qweb template yeay !) - fix FSM access groups - rewrite the flow of a FSM task with a state machine: record time, validate, invoice, send report, ... See subcommits for more details. A phase 3 is plan to still improve this "so quickly merged" feature. Task-1943792
Adds predictive scoring to CRM leads so sales teams can better prioritize opportunities based on their likelihood to convert. The update includes company-level settings, stage controls, manual score overrides, and daily recalculation to keep lead probabilities current.
Resolved issues and error corrections
Manufacturing BOM structure PDF reports now include the same product and sub-BOM details shown on screen. The unfolded PDF printout also respects the quantity selected by the user, making printed reports more accurate and consistent.
Original PR description
1. Because of BOM Version and ECOs not printed in BOM Structure report, the pdf report is not printed in proper manner. It is different than html view. So adding product_id and child_bom in BOM line to fix this, Now report is printed properly. 2. After updating quantity, print unfolded pdf did not print that quantity in bom lines. It should be like html view and print default pdf. Now, after this fix, updated quantity is affected to print unfolded pdf, same as html view and default print. Issue : https://www.odoo.com/web#id=1939278&action=333&active_id=1278&model=project.task&view_type=form&menu_id=4720 pad : https://pad.odoo.com/p/openerp-project.task-4WE13BXFUY -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves manufacturing planning by correcting finished move lead time handling and adjusts purchase stock demo data. The demo change makes it easier to create a production order that automatically triggers multiple purchase orders for desk components.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects small usability issues in sales quotations and partner assignment pages. Users should see cleaner quotation messages and be able to update next activities and dates reliably again.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update aligns recently merged changes with Odoo's newer debugging setup and test organization. It helps prevent related web editor and comparison shop features from breaking after platform updates, with no expected change to normal user workflows.
Original PR description
https://github.com/odoo/odoo/pull/33213 introduced a new debug and new asset. But some commits were merge simultaneously and/or forward ported from lower version. Those commits needed to be adapted.
This update adjusts the timing tolerance used in automated planning tests so they are less likely to fail when execution is slower than usual. It does not change business functionality, but helps keep validation of manufacturing and stock-related processes more stable.
Original PR description
The tests relative to workcenters planning takes (sometimes) long time to be executed. Before investigation more deeply, this commit relax a bit more the tolerance delta in the test comparison Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where restaurant bill printing still referenced a removed POS shop value, which could cause receipts or bills to fail. It also ensures POS configurations use the correct company currency, improving accuracy in multi-company setups.
Original PR description
The variable 'sop' that was set for POS receipt, was actually the stock location and has been removed. But we forgot to remove its use in pos_retaurant. related commit: 8e30349fd1f2baffd47e50106eddbd1c59979aaf Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The BOM PDF report now displays BOM lines correctly, including version and engineering change order information. This helps users review manufacturing documentation more accurately and access related change records from the report.
Original PR description
Previously, In BOM pdf report, BOM lines are not printed in proper manner because of version and ecos are not displayed. This fix improves the BOM line behaviour properly. Issue : https://www.odoo.com/web#id=1939278&action=333&active_id=1278&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/openerp-project.task-4WE13BXFUY
The point of sale payment screen now safely handles cases where no order has been started yet. This prevents an unexpected error from interrupting payment-related workflows for stores using connected IoT payment devices.
Original PR description
**Task**: https://www.odoo.com/web#id=2005903&model=project.task&menu_id=4720 **Pad**: https://pad.odoo.com/p/r.a6bf43ff079f2c4cd28963af229656e6 --
This fixes how Mexican electronic invoicing product code records are marked so they are not accidentally deleted when the module is updated. It helps preserve required invoicing reference data and avoids disruption after upgrades.
Original PR description
Enterprise version of odoo/odoo#32881 cc @nhomar cf the comment about l10n_mx_edi
Code cleanup and technical improvements
The website module’s code has been reorganized into several focused files instead of one large file. This internal cleanup makes the system easier for developers to maintain and should not change how users experience the website features.
Original PR description
Split class from file addons/website/model/website.py in multi files. Make several commit: new file, move code, merge by class to keep history clean.
This update restructures how inventory value changes are recorded, preparing Odoo to use dedicated stock valuation layers instead of older price history records. It also improves consistency when valuing purchase returns and makes required accounting setup clearer for users.
Original PR description
task-1875873
The master production schedule has been redesigned to better reflect real demand, replenishment already in progress, and warehouse-specific planning. This helps planners adjust forecasts after procurement starts, plan across multiple warehouses, and use clearer schedule views with improved guidance.
Original PR description
The purpose of this commit is to redo master production schedule with the purpose to: - Have a better integration with existing records. For demand forecast and replenishment it adds a tools in order…
The purpose of this commit is to redo master production schedule with the purpose to: - Have a better integration with existing records. For demand forecast and replenishment it adds a tools in order to show the actual demand and the actual replenishment. Also running the replenishment will deduce the value to replenish with the existing replenishment already in progress. - Flexibility on already launched forecast. If the user modify the demand forecast or the quantity to replenish after the procurement creation, it will allow the user to relaunch the cell in order to complete replenishment. - Multiple warehouses management - Allow to define a custom number of periods. It would allow use case with long manufacturing process - The rules lead time is added to manufacturing and suppliers delay. It is usefull if the transfer are long between 2 warehouses as example. Visual effect for the end user: - Remove the period from the control panel because the user could modify it without modification on the min and max replenishment for each schedule, it would completely modify the future forecast and create a lot of inconsistent documents. (Still available in configuration). - Use the total width on the screen in order to shpow the information more clearly on the screen - Apply button on schedule with a BoM linked to other MPS is replaced by a direct reload on impacted schedule. - Hover on replenish button that highlight the forecast that will be run. The replenish button in control panel is based on lead time, the replenish button on row, will run the next forecast. - Tooltips on each row in order to explain the purpose.
Inventory value reporting now uses valuation layer data so reported inventory values better reflect the current financial valuation. Subscription access is adjusted after product price history removal, and SEPA direct debit payment processing is fixed for invoices opened under the updated flow.
Original PR description
Use the valuation layers instead of move.value. "Inventory value" should always contain the valuation right now. task-1875873