Daily updates from Odoo
Navigate
Branch
Monday, August 19, 2019
34 changes
New functionality added to Odoo
Odoo now records website visitor activity, links visitors to leads or customer records when they engage, and gives live chat operators the ability to start conversations with available visitors. This helps sales and support teams understand recent visitor behavior and reach out at the right moment.
Original PR description
This merge adds the website_visitor model that will be used to track website visitor activity (page viewed, number of visits and more general info about the visitor (country, lang, etc..) This model…
This merge adds the website_visitor model that will be used to track website visitor activity (page viewed, number of visits and more general info about the visitor (country, lang, etc..) This model will, in later commit, be used to send chat requests and push notification from the operators (or backend users) directly to the visitor. To keep a detailed history of the visitor page views, we add a website.visitor.page model that makes the link between visitor and website.page but that keeps the visit date. So that we can see if a visitor went mulitple times on the same page and when. It's useful to see his last page views. If a website_visitor submit a contact form (and becomes a lead), the website_visitor is linked to the crm.lead. If a website_visitor logs in, the website_visitor is linked to the user's res.partner. This also allows a livechat operator to send a chat request to a connected and available website_visitor. See sub commits for more detailed informations about functional flows and technical changes/decisions. Task : https://www.odoo.com/web?#id=2028059&action=327&model=project.task&view_type=form&menu_id=4720 Linked to enterprise PR odoo/enterprise#4834
Odoo can now value delivered stock based on the exact serial or lot numbers selected, rather than only using the oldest available stock costs. This improves warehouse accounting accuracy when identical products are received at different costs and later shipped by specific serial number.
Original PR description
This PR adds Stock Valuation Identification Method support for Warehouse Accounting. Assume that we have - Day 1: stock `in 2` pc @ `$100` with Seials `0001` and `0002` - Day 2: stock `in 2` pc @…
This PR adds Stock Valuation Identification Method support for Warehouse Accounting. Assume that we have - Day 1: stock `in 2` pc @ `$100` with Seials `0001` and `0002` - Day 2: stock `in 2` pc @ `$200` with Seials `0004` and `0005` - Day 3: stock `in 2` pc @ `$300` with Seials `0006` and `0007` - Day 4: stock `out 3` pc `0001`, `0004`, `0007` ### Current behavior before PR: Odoo does not respect the serials input during delivery then it valuates only 100+100+200 = 400 (serials 0001, 0002, 0004 respectively) ### Desired behavior after PR is merged: The out valuation should be 100 + 200 + 300 (serials 0001, 0004, 0007 respectively) ### What this PR does 1. [IMP] move methods `_create_%s_svl` from stock move to stock move line for more relevant and shorter code. It also helps later development of Valuation Identification Method 2. [ADD] fields `stock_move_line_id` and `lot_id` to stock.valuation.layer 3. [ADD] method `_run_fifo` now supports Stock Valuation Identification Method if lots are passed into the method. It does the job by * finding back incomming stock valuation layers having lot/serial first * comparing the quantity with lots with the initial fifo quantity. If the quantity with lots is less, continuing to find other candidate. * after these operations, the candidates with lots will be on the top of the recordset for later valuation -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
Restaurant staff can now work from the same Point of Sale configuration and share a single session across devices. Orders and table activity are synchronized when switching tables, helping multiple waiters serve the same floor without blocking each other.
Original PR description
PURPOSE ========= When working in restaurants, there are often more than one waiter working on the same floor. But Odoo doesn't support that. There can only be one person working on one session for…
PURPOSE
=========
When working in restaurants, there are often more than one waiter working on the same floor.
But Odoo doesn't support that.
There can only be one person working on one session for the same tables.
The purpose of this task to allow several people to work on the same session (while synchronizing sessions).
SPECIFICATIONS
===============
- MultiUser is active by default.
- Allow multiple waiters to login on one PoS Config.
- All waiters login to the same session, the waiter that does the paiment is the responsible for the order (same as now).
- Synchonize the information across the multiple instances running on same floors.
Syncronisation will take place at switch of table.
(close tables automaticly if no activity, to force sync)
- Syncro cannot be done if no internet : how do we manage it ? We should inform the user the internet connection has been lost and that synchro cannot be done. What impacts? To check
Useful links
https://github.com/it-projects-llc/pos-addons
https://apps.odoo.com/apps/modules/11.0/pos_bus_restaurant/
Related PR:
https://github.com/odoo/odoo/pull/32789
task: https://www.odoo.com/web#id=1891130&model=project.task&view_type=form&menu_id=When installing a language, Odoo now keeps the translation overwrite option enabled by default while hiding the choice from users. This makes language setup behave more consistently and reduces the chance of outdated translations remaining after installation.
Original PR description
Following 43d355c2084, same logic Hide it but make it checked by default
Event managers now see attendees in a Kanban card view when using the Attendees button from an event. This makes attendee information easier to scan visually compared with the previous list-only view.
Original PR description
Description of the issue/feature this PR addresses: Task link - https://www.odoo.com/web?#id=1935268&action=327&model=project.task&view_type=form&menu_id=4720 Pad link - https://pad.odoo.com/p/r.1af96af212e96802e1a8d6445236a2c0 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 mail app’s Discuss area was adjusted to better support mobile use, especially responsive layouts and swipe-friendly message previews. This prepares the messaging experience for smoother mobile interactions while keeping shared code easier to reuse.
Original PR description
Task ID : 1895453
Odoo now stores selectable field options as dedicated records, making them easier to manage by module. This helps translations stay tied to the right module and ensures removed modules clean up their related choices more reliably.
Original PR description
Store selections in ir.model.fields.selection No change in the declaration of fields https://www.odoo.com/web#id=27028&action=333&active_id=1364&model=project.task&view_type=form&menu_id=4720 https://pad.odoo.com/p/r.3e1ec17b8af9afedbd501db256072a99
The employee profile screens have been reorganized to make key information easier to find and manage. This improves day-to-day HR work by reducing clutter and creating a clearer experience across employee and related user forms.
Original PR description
TaskID: 2054559 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
Tax report line names and tag labels can now be translated for multilingual users. This helps businesses present tax report configuration clearly in the user's language, especially where tax reporting is country-specific.
Original PR description
…name of model account.tax.report.line - both the name and the tag_name made translate=True defined inside class account.tax.report.line task : 2042430 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update prevents users from deleting records that are still needed by active Point of Sale sessions or configurations. It helps avoid broken sales workflows and configuration inconsistencies when related customers, employees, picking types, sequences, or accounting records are in use.
Original PR description
The deletion of some records can create inconsistencies in the point_of_sale. It can create inconsistencies when a session is open, for example if you delete a partner that can be set on a pos order. You'll also got problems if you remove an employee and this employee can be used in an open session. We also avoid to get point_of_sale config inconsistencies, by deleting models required by it. If you delete a picking type used in a pos config or a sequence. To avoid all this consistencies, we have restricted the deletion of some records in specific cases. TASK-ID: 1879971 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 product matrix used in sales and purchasing has been refined to make selecting product variants clearer and smoother. This should help teams enter orders with multiple variants or extra prices more accurately and efficiently.
Original PR description
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Point of Sale interface has been adjusted to make navigation easier for B2B workflows. This should help sales teams find products, categories, orders, and related PoS information more quickly during customer interactions.
Original PR description
TASK-ID: 2050245 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update makes project task reports easier to extend by preventing field name conflicts when businesses customize reporting views. It also improves readability in project task cards and supports clearer visual identification in Gantt planning through optional thumbnails.
Original PR description
Aliasing the fields in the select clause of the task report allow to do joins latter when inheriting from this object without getting ambiguous fields errors. related task 2009563 Description of the issue/feature this PR addresses: Current behavior before PR: Overriding the query to generate a different report, when joining on project_project table, we get a ambiguous column error Desired behavior after PR is merged: Overriding the query to generate a different report, when joining on project_project table everything works as expected. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Restaurant staff can now work together on the same point-of-sale session for shared tables and floors. This helps teams serve customers more smoothly by keeping activity synchronized between multiple waiters.
Original PR description
PURPOSE
=========
When working in restaurants, there are often more than one waiter working on the same floor.
But Odoo doesn't support that.
There can only be one person working on one session for the same tables.
The purpose of this task to allow several people to work on the same session (while synchronizing sessions).
TASK-ID: 1891130German Datev exports can now use a dedicated identifier on partner records, making it easier for companies migrating to Odoo to keep their existing Datev numbers. If no identifier is provided, Odoo automatically assigns one from a configurable starting range to avoid conflicts with account numbers.
Original PR description
…r Datev export When migrating to Odoo, people want to keep their old Datev identifiers. As the identifier was set to the id of the partner in Odoo, this was not possible. So, we decided to add a field for the datev identifier on the partner which allows to import the old number. If it is not set we set it by default to 100000000 + the id. This way, we also avoid conflicts with the account numbers. You can also change the 100000000 by setting a system parameter l10n_de.datev_start_count Task ID : 1942108
The event barcode scanning screen has been refreshed to better match the attendee and point-of-sale interfaces. Event staff can now also search for attendees directly from the scanning screen, making check-in workflows faster and easier.
Original PR description
Description of the issue/feature this PR addresses: Task link - https://www.odoo.com/web?#id=1935268&action=327&model=project.task&view_type=form&menu_id=4720 Pad link - https://pad.odoo.com/p/r.1af96af212e96802e1a8d6445236a2c0 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](http://www.odoo.com/submit-pr)
Mobile users can now swipe messages to quickly mark them as read or add a star, making inbox triage faster in Discuss and the messaging menu. The update also adds an undo snackbar so users can easily reverse these quick actions if needed.
Original PR description
You are now able to: Swipe (LTR) to mark a message as read Swipe (RTL) to star a message. Task ID : 1895453
The employee form has been refined to make HR information easier to view and manage. This improves day-to-day usability for HR teams and related payroll or appraisal workflows without introducing a major functional change.
Original PR description
TaskID: 2054559
Calendar event details now open in a full-screen popover on mobile devices instead of a small floating box. This makes the information easier to read and use on smaller screens.
Original PR description
Before this commit, the popover used in calendar was a normal Bootstrap popover but the position and the size wasn't optimal for small screens. After this commit, the popover takes the whole screen. Task ID : 2052506
The Field Service app now has clearer menus, ready-made filters, map and calendar views, planning views, and task reporting to help teams organize daily work faster. Managers can more easily review all jobs, assign work, see customer locations, and analyze field service tasks, while some complex setup options were simplified.
Original PR description
This merges provides many UI changes in order to improve the usability and day to day work of FSM application. This adds - news menus - news predefined filters - reorganise some views - reporting for worksheet - simplify some options (allowed products, ...) See subcommits for more details Task-2009563
Resolved issues and error corrections
This update removes leftover debugging code from the restaurant point of sale module. It keeps the codebase cleaner and helps avoid confusion for future maintenance, with no expected change for everyday users.
Original PR description
Forgot to remove unused function with pudb in a248171d96de3ad6d8e22c855886dfae61e145e2 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 the Sales CRM area used the wrong date field after a recent change. It helps keep sales reporting and related CRM information aligned with the correct dates.
This fixes an error that could occur when adding a new section to an online course from the website. Course managers can now organize course content into sections without being interrupted by a system traceback.
Original PR description
Description of the issue/feature this PR addresses: Task ID: https://www.odoo.com/web?#id=2053822&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 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
Receipt styling now loads correctly in Point of Sale, so printed receipts use the expected layout. This prevents formatting problems that could cause receipt printing to fail for cashiers and customers.
Original PR description
The CSS for receipts to be printed was not loaded correctly in the POS. The format of the receipt was wrong and the printing failed. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Returned delivery items are now correctly marked so sales orders automatically reduce the delivered quantity when a refund return is created. This keeps sales and inventory records aligned and helps prevent incorrect refund or fulfillment information.
Original PR description
When create a return from a delivery order, the field `to_return` must be True, so the delivered quantity of the sale order will be updated by default. But it wasn't the case before this commit ! Thus, adds a test to be aware in the case something goes wrong again. Task #2050183
The Salary Package Configurator app now uses the same Human Resources category label as related payroll apps. This prevents duplicate app categories and makes the apps list cleaner and easier to navigate.
Original PR description
See https://github.com/odoo/odoo/issues/34531 Fixes https://github.com/odoo/odoo/issues/34531 It fixes the following issue: > This is because the app hr_contract_salary has "Human Resource" in its manifest while the app l10n_in_hr_payroll has "Human Resources" in its manifest.
This update fixes a typo in the map settings description and adds missing translated text. It helps users see clearer, properly localized wording when configuring map-related options.
Original PR description
Fixes a typo in the field description and adds missing translation terms
Merchant receipts in Point of Sale are now sent to the IoT Box using the correct check. This ensures businesses receive the expected printed merchant copy after payments, reducing missed paperwork and manual reprints.
Original PR description
We didn't check the correct variable before sending the receipts for merchants to the IoT Box to be printed.
Features or functions removed from Odoo
Website contact form leads are now linked through the website visitor record instead of a separate lead cookie. Obsolete page-view tracking in Website CRM Scoring was removed because visitor history already stores the useful browsing information.
Original PR description
Since introduction of website_visitor, there is no need to keep the lead identification via lead_id cookie when contact_form is sent. Each time contact form is sent, a new lead is created and linked to the visitor_id. So all the leads are linked between them to the same visitor_id. Lang_id has been moved to crm module. Has it's interesting to store the lang of the lead, for marketing or follow up reason. Pages_viewed machanism has been totally deleted. The pages viewed by the lead is in fact stored on the website_visitor. But anyway, this pages_viewed cookie was never set and was then unusable. This commit is linked to community commit from https://github.com/odoo/odoo/pull/34624 Task ID : 2028059
Code cleanup and technical improvements
This update streamlines subcontracting by moving key actions directly onto operations, supporting extra received quantities, dropshipping flows, and easier tracking of lots and components. It also simplifies setup by allowing any supplier to be assigned on a bill of materials, reducing configuration overhead and improving day-to-day accuracy.
Original PR description
This PR modify the subcontracting process: - Support extra quantity - No more interaction with the subcontract order. Everything is directly accessible on the operation - Dropshipping with subcontracting - Bypass reservation process - The partner type subcontractor is removed and every partner could be set on the BoM - Update the initial demand will trigger the rules. - Demo data - Subcontractor is required on the BoM (no more BoM for all partners of type subcontractor) Visually: - Remove the stat button for linked operation. - Register Components is only available when a subcontract component is tracked - Button on operations in order to correct tracked components - Show Operation button will ask to record components until the total quantity is provided(correction on finish lines are allowed after) More details available in each commit Task 1962187
The calendar view code was reorganized so the popover shown for calendar items can be customized more easily, especially for mobile experiences in the enterprise edition. This is an internal cleanup that supports better mobile behavior without changing day-to-day functionality for most users.
Original PR description
This commit move some code to be able to override Bootstrap popover in web_enterprise for mobile. Task ID : 2052506 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo Studio now uses the shared field selection records introduced in the core platform. This keeps Studio aligned with the underlying system model and should make future maintenance more consistent without changing day-to-day user workflows.
Original PR description
web_studio: use ir.model.fields.selection Following odoo/odoo#30228
The Austrian reporting localization has been fully reworked after years of minimal maintenance. This should provide a stronger, more consolidated foundation for Austrian financial reports and future improvements.
Original PR description
**Description of the issue/feature this PR addresses:** Austrian Localization completely refactored Odoo Community: https://github.com/odoo/odoo/pull/35642 @jco-odoo Let's do it :wink:
Documentation and clarification updates
This pull request adds Trilab's signed contributor agreement to Odoo's records. It supports compliance and confirms the company's authorization to contribute to the project.
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