Daily updates from Odoo
Navigate
Branch
Friday, September 3, 2021
23 changes
New functionality added to Odoo
Project tasks now show a warning when the assigned employee is on time off during the planned work period, making scheduling conflicts easier to spot. Users can also filter for tasks in conflict, helping managers quickly find and resolve availability issues before work is assigned.
Original PR description
Purpose of the task is to display the warning stating that an employee is on holiday at the time the task is planned would reinforce the feature. In addition, the fact that a given cell is grey in the Gantt view can easily be overlooked if a task was already planned for this user before he took that day off. So in this commit, - Added the module to integrate the tasks with time off and display the warning on task when the user is on leave. - also added the filter to find the task on which the user is on leave - also move the conflict warning (and decoration) from Field Service to Project and added a 'tasks in conflict' filter on tasks. Related Enterprise Upgrade: odoo/upgrade#2803 TaskID: 2453321
Users can now add links in Documents spreadsheets that open specific Odoo menus or saved views. This makes spreadsheet templates more actionable by connecting reports or planning sheets directly to the relevant business screens, though some access-limited menus may not be available.
Original PR description
See commit messages :)
Enhancements to existing features
Timesheet reports grouped by billing type now include a grid view. This makes it easier for teams to review and compare billable time information in a structured layout.
The timesheet settings page has been made clearer and easier to use, with updated labels, descriptions, mobile layout improvements, and clearer service navigation. Community users will also see key Enterprise-only options marked consistently, helping them understand available upgrade features.
Original PR description
…e timesheet module The purpose of this task is to improve the setting of the timesheet module. In this commit, we improve the following: - Rename the label, description and align the field with the name and description of the feature - Add an 'OK' button in the 'download our app' modal - Render the frequency field properly in the employee/manager reminders setting on mobile view - In configure your services link: change the name of the action to "Services" - Display the following options in the community, with the usual 'Enterprise' tag: Round Timesheet, Employee/Manager reminder, Invoicing Policy Task-Id: 2531338 PR: #20182
Field service task costs now use the task's own analytic account first, falling back to the project account when needed. This improves accounting accuracy for task-level profitability and removes an unnecessary customization around sales order line mapping.
Original PR description
Previously, all costs allocated to a task were associated, if set, to the analytic account of their project. Prior to this PR, the sale order line in the project employee mapping was redefined to remove the required option. With this PR, we now use the analytic account of the task and then the one defined on the project (using the computed field which makes the computation). It removes the override since the field is already defined as not required in its first definition. PR community: odoo/odoo#70527 PR upgrade: odoo/upgrade#2616 task-2458135
The event form now places the Registration Desk shortcut beside the Attendees shortcut. This makes the event screen more intuitive and keeps related event check-in actions grouped together regardless of module installation order.
Original PR description
PURPOSE The 'Registration Desk' stat button should be appear next to 'Attendees' stat button. The purpose of this commit is to re-arrange 'Registration Desk' stat button and set it after the 'Attendees' stat button. SPECIFICATIONS Currently, if the event_barcode module is installed, the 'Registration Desk' stat button is placed after 'Leads' stat button on the event form view. This improves the inheritance priority and the x-path of the 'Registration Desk' stat button by placing it after the 'Attendees' stat button. This is the goal of this commit. LINKS PR #20082 TaskID-2585998
Barcode scanning is updated to use standard browser camera and barcode detection capabilities instead of relying mainly on native mobile app functions. This makes the experience more consistent across supported devices, while also moving small-screen web behavior into the enterprise web module and using Odoo notifications and device vibration where available.
Original PR description
This PR aims at replacing as much mobile app's native APIs (cf. `mobile.methods`) by their equivalent Web APIs. More specifically, it targets the barcode scanning feature by using the device's camera…
This PR aims at replacing as much mobile app's native APIs (cf. `mobile.methods`) by their equivalent Web APIs. More specifically, it targets the barcode scanning feature by using the device's camera through `getUserMedia`and Shape Detection API (or a lightweight polyfill, depending on the browser support). In this process, some other methods like `vibrate` or `showToast` are also replaced by, respectively, their Web equivalent or the Odoo notification system. Finally, this PR is the opportunity to refocus the `web_mobile` module's content to its primary purpose: provide support for the native mobile apps (leaving the responsive part to `web_enterprise`). Note: this feature requires a secureContext (aka. HTTPS) to be available. References: - https://developer.mozilla.org/en-US/docs/Web/API/BarcodeDetector - https://github.com/zxing-js/library - https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia Task ID: 2583914 Co-authored-by: Romeo Fragomeli <rfr@odoo.com> Co-authored-by: Pierre Paridans <app@odoo.com>
Barcode picking screens now show extra kit bill of materials information when a purchased kit product is split into its component items. This helps warehouse users understand why component lines appear and improves visibility during stock handling, with a related update to product form availability buttons in rental sales.
Original PR description
Whenever there is a kit bom for a product, we consider this product a kit product. When purchase a kit product, it will be decomposed in the picking. In barcode operation, we add a new line to show the bom info when the product is coming from a kits.
This update improves how several Odoo Enterprise screens work on mobile devices, especially control panels and reporting views. It also updates spreadsheet pivot reporting foundations so business data views remain reliable after the newer interface changes.
The accounting report test suite was updated to stay aligned with recent related changes in the main Odoo codebase. This helps ensure tax and point-of-sale accounting reports continue to be validated reliably without introducing direct user-facing behavior changes.
Original PR description
Task: 2453325
Users who can view but not edit documents can now open spreadsheets without hitting an access error. The interface clearly limits editing tools while still allowing safe changes to existing filter values, making shared spreadsheets easier to use for read-only users.
Original PR description
task [2572290]( https://www.odoo.com/web#cids=1&id=2572290&menu_id=4720&model=project.task )
Resolved issues and error corrections
Authorized users can now edit their document spreadsheet templates as intended. This fixes an access check issue that incorrectly blocked legitimate template updates, reducing friction for teams managing reusable spreadsheet content.
Original PR description
the access check on "write" operation was badly handled and would be falsy all the time, preventing an authorized user to edit a template. Task 2637277
The Studio model setup screen now includes the missing Lines option again. This lets users automatically create related line items when configuring a new model, restoring expected functionality after a prior interface migration.
Original PR description
PURPOSE Lines option in model configurator is missing in master, add lines option in model configurator. SPEC Lines option should be available in model configurator. TASK 2610955
This fixes an issue that could prevent the website appointment editor helper from opening the correct appointment form. The change keeps appointment website editing working after underlying system changes, reducing disruption for users managing bookings online.
Original PR description
The `xmlid_to_res_model_res_id` method cannot be called through RPC since c7bac3dee0bbc8b9e3d0e2dda419f3875916d96e. Use `form_view_ref` in context instead. As a matter of fact, the xml_id of the view itself changed from saas-14.4 to now, so it had to be fixed as well. Why neither of those two changes were reflected on this file remains a mystery to me but this is now fixed. Task id 2636397.
This update fixes minor issues in the project planning chart introduced by an earlier change. It removes redundant behavior and improves how dependency connectors appear, helping users read task relationships more reliably.
Original PR description
This PR addresses some issues introduced in PR #18045
Invoice reports were showing unwanted spacing after a change to the invoice comments editor. This fix updates the affected report layouts so invoices render neatly across several localization and payment modules.
Original PR description
Since we change the editor for the comments on invoices, The layout was a bit broken with some unwanted spacings. We change the view to fix this, so some xpath had to be adapted. task-2586137
This fix stops an error from appearing when a user adds an employee to a task forecast that did not previously exist. It makes project planning smoother by allowing teams to schedule task work without interruption.
Original PR description
Steps to reproduce: - Enable planning in project - Select a project, select a task with no forecast - Click on the Forecast smart button - Add an employee - A traceback appears Observed behavior: - A traceback appears Expected behavior: No traceback task-2636356
This fix corrects the name of a view used by the appraisal survey feature. It helps keep the appraisal interface properly labeled and avoids confusion for users working with employee reviews.
Original PR description
task - 2528209
Code cleanup and technical improvements
This update modernizes how Odoo manages background database work and business transaction state. It should make the platform easier to maintain and more reliable without changing day-to-day user workflows.
Original PR description
Linked to https://github.com/odoo/odoo/pull/75598.
The PLM bill of materials structure report was cleaned up by removing unused display logic and obsolete styling hooks. This keeps the report behavior consistent while making future maintenance easier and reducing the risk of confusing report differences.
Original PR description
The code of `_reload_report_type` for plm wasn't correct (there isn't a `report_type === 'bom_cost'` ). Then remove this code to keep the same behaviour. Then the classes `o_mrp_bom_ver` and `o_mrp_ecos` wasn't used, then remove it. Also simplify template because of `_get_extra_column_count`. See odoo/odoo#75041 See odoo/upgrade#2750
Miscellaneous changes
Steps to follow to reproduce the bug: - Create a German company - Go to accounting settings / in “Fiscal Localization” install German-Accounting - Create any journal entries - Go to Reporting / General Ledger > Export DATEV - Open generated CSV Problem : In the "belegdatum" field, the date is not formatted as "DDMM", like mentioned in the official DATEV documentation (cf: https://apps.datev.de/dnlexka/document/1003221#D162129592909910539). Dates must have this format "DDMM", e.g: - 0
Original PR description
Steps to follow to reproduce the bug: - Create a German company - Go to accounting settings / in “Fiscal Localization” install German-Accounting - Create any journal entries - Go to Reporting / General Ledger > Export DATEV - Open generated CSV Problem : In the "belegdatum" field, the date is not formatted as "DDMM", like mentioned in the official DATEV documentation (cf: https://apps.datev.de/dnlexka/document/1003221#D162129592909910539). Dates must have this format "DDMM", e.g: - 01.06.2020 → 106 - 22.03.2020 → 2203 opw-2632606 Forward-Port-Of: odoo/enterprise#20585
PURPOSE When wanting to add a stat button to any model in Odoo using Studio I get the following error every time, no matter where : "Custom field names cannot contain double undescores." Stat button should not fail while adding. SPEC Add stat button successfully without any warning. TASK 2621375 Forward-Port-Of: odoo/enterprise#20267
Original PR description
PURPOSE When wanting to add a stat button to any model in Odoo using Studio I get the following error every time, no matter where : "Custom field names cannot contain double undescores." Stat button should not fail while adding. SPEC Add stat button successfully without any warning. TASK 2621375 Forward-Port-Of: odoo/enterprise#20267
Add a new provider - https://www.centralbank.ae/en/fx-rates Task 2615290 Forward-Port-Of: odoo/enterprise#20582
Original PR description
Add a new provider - https://www.centralbank.ae/en/fx-rates Task 2615290 Forward-Port-Of: odoo/enterprise#20582