Daily updates from Odoo
Thursday, January 8, 2026
24 changes
2 changes
Enhancements to existing features
This update enhances the Thai version of Odoo by improving its chart of accounts, tax templates, and asset configurations. These changes are designed to improve compliance with Thai tax regulations and provide a better user experience for businesses operating in Thailand. This ensures accurate financial reporting and simplifies tax management.
Original PR description
Expanded and updated the Thai localization with an enhanced chart of accounts, updated tax templates, asset templates, and tax group configuration for better compliance and usability. Task-5395076 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#240668
This update adds crucial data attributes to tax calculations and NFS-e submissions when the Brazilian fiscal reform is active. Specifically, the system now transmits the 'name', 'businessName', 'federalTaxId', and 'type' attributes, ensuring accurate tax reporting and compliance with new regulations. This improves the reliability of tax processing for Brazilian businesses.
Original PR description
Purpose: Additional attributes are required to be sent in the rendered node for tax calculation and NFS-e submission when the fiscal reform is enabled. The additional required attributes are: - name - businessName - federalTaxId - type task-5450129 Forward-Port-Of: odoo/enterprise#103438
1 change
Enhancements to existing features
This update adds crucial data attributes to tax calculations and NFS-e submissions when the Brazilian fiscal reform is active. Specifically, the system now includes 'name', 'businessName', 'federalTaxId', and 'type' fields, ensuring accurate tax reporting and compliance with new regulations. This change supports the ongoing requirements of the Brazilian tax system.
Original PR description
Purpose: Additional attributes are required to be sent in the rendered node for tax calculation and NFS-e submission when the fiscal reform is enabled. The additional required attributes are: - name - businessName - federalTaxId - type task-5450129 Forward-Port-Of: odoo/enterprise#103438
1 change
Enhancements to existing features
This update adds crucial data attributes to Odoo's tax calculations and NFS-e submissions when the Brazilian fiscal reform is active. Specifically, the system now includes 'name', 'businessName', 'federalTaxId', and 'type' fields, ensuring accurate tax reporting and compliance with new regulations. This change is necessary to meet updated Brazilian tax requirements.
Original PR description
Purpose: Additional attributes are required to be sent in the rendered node for tax calculation and NFS-e submission when the fiscal reform is enabled. The additional required attributes are: - name - businessName - federalTaxId - type task-5450129 Forward-Port-Of: odoo/enterprise#103438
1 change
Enhancements to existing features
This update adds crucial data attributes to Odoo's tax calculations and NFS-e submissions when the Brazilian fiscal reform is active. Specifically, the system now includes 'name', 'businessName', 'federalTaxId', and 'type' fields, ensuring accurate tax reporting and compliance with new regulations. This change improves the reliability of tax calculations for Brazilian businesses.
Original PR description
Purpose: Additional attributes are required to be sent in the rendered node for tax calculation and NFS-e submission when the fiscal reform is enabled. The additional required attributes are: - name - businessName - federalTaxId - type task-5450129 Forward-Port-Of: odoo/enterprise#103438
14 changes
Enhancements to existing features
This update introduces a new button within the holiday attest form, streamlining the process for directly allocating paid time off. Previously, users had to navigate through multiple steps to create an allocation; now, they can do it more quickly and efficiently. This improves user experience and reduces administrative overhead.
Original PR description
In this PR, we added a button in the holiday attest in the year n1 to ease the flow of creating an allocation directly. task-5214143.
This update improves the payment reporting process by allowing the inclusion of unpaid payslips in single payments and adjusting report formats (CSV, SEPA) to reflect the new logic. The 'Include partners' feature has been removed, and the revert action now correctly marks payslips as paid, enhancing reporting accuracy and usability.
Original PR description
New adjustments have been introduced to the payment flow: -Include unpaid feature to include other "validated" payslips in the same payment. -CSV and SEPA formats for payment report have been adjusted to adhere to the new logic accordingly. -"Include partners" feature has been removed. -Revert action now marks both payslips as "paid". -Payslip report for My company,US,AU,CH companies has been enhanced for better readability. -Batch account move line settings has been clarified. -Some minor UX changes in the payment report wizard. Task: #5388635
This pull request updates the core spreadsheet component within Odoo. It includes several improvements and bug fixes related to functionality, performance, and user experience, specifically enhancing the spreadsheet editor and conditional formatting features. These changes ensure the spreadsheet remains a reliable and efficient tool for managing data.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/ac2fa3e6d4 [REL] 19.2.0-alpha.2 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/ac2fa3e6d4 [REL] 19.2.0-alpha.2 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0) https://github.com/odoo/o-spreadsheet/commit/811ec6d6d2 [FIX] session: always return a Promise [Task: 0](https://www.odoo.com/odoo/2328/tasks/0) https://github.com/odoo/o-spreadsheet/commit/900df13338 [FIX] session: recover from errors when sending messages [Task: 5469116](https://www.odoo.com/odoo/2328/tasks/5469116) https://github.com/odoo/o-spreadsheet/commit/f832009ebf [REF] side_panel: rename CSS classes for clarity [Task: 4982596](https://www.odoo.com/odoo/2328/tasks/4982596) https://github.com/odoo/o-spreadsheet/commit/ada17cb231 [REF] side_panel: split CF into main and editor panels, use store [Task: 4982596](https://www.odoo.com/odoo/2328/tasks/4982596) https://github.com/odoo/o-spreadsheet/commit/c3ee9f24ab [REF] side_panel: separate data validation list and editor logic [Task: 4982596](https://www.odoo.com/odoo/2328/tasks/4982596) https://github.com/odoo/o-spreadsheet/commit/f255b8720d [FIX] data validation: fix date criterion [Task: 5343580](https://www.odoo.com/odoo/2328/tasks/5343580) https://github.com/odoo/o-spreadsheet/commit/f19bf803a4 [IMP] cf: add top10 conditional formatting operator [Task: 5367065](https://www.odoo.com/odoo/2328/tasks/5367065) https://github.com/odoo/o-spreadsheet/commit/559cdd8ff1 [FIX] dashboard: properly handle grid resize in dashboard mode [Task: 5223156](https://www.odoo.com/odoo/2328/tasks/5223156) Co-authored-by: Florian Damhaut (flda) <flda@odoo.com> Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com> Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com> Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com> Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com> Co-authored-by: Ronak Mukeshbhai Bharadiya (rmbh) <rmbh@odoo.com> Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com> Co-authored-by: Rémi Rahir (rar) <rar@odoo.com> Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com> Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com> Co-authored-by: Marceline Thomas (matho) <matho@odoo.com>
This update simplifies the way data extraction groups related boxes, allowing users to select and manage multiple boxes at once. This enhancement improves the user experience and efficiency when working with large datasets. The underlying CSS has also been cleaned and optimized for better performance.
Original PR description
**[IMP] iap_extract: group boxes into selectable columns** The boxes that are vertically aligned and close together are now grouped into a column that can be clicked to select all the contained boxes at once. If similar columns are found on the next pages, they will be selected as well. task-[5177261](https://www.odoo.com/odoo/project/2068/tasks/5177261) This is how it looks like in practice (right column is being hovered, left one isn't): <img width="505" height="228" alt="image" src="https://github.com/user-attachments/assets/422817b0-f08f-4ba2-88a1-ba6265e85739" /> --- **[CLN] iap_extract: clean CSS file of manual_correction component** This CSS file was a bit of a mess, it's been simplified and factorized where it could be. It should be strictly equivalent to the old file. Forward-Port-Of: odoo/enterprise#102812
This update simplifies event slot creation by allowing users to confirm and adjust event time ranges when adding slots outside the original event timeframe. It also enhances the user interface with a new 'Slots' button and a more intuitive form dialog for slot creation, improving overall usability.
Original PR description
Purpose ======= Improve the event slots feature and some other small improvements. Specification =========== Event form: - Add a "Slots" stat button to ease access to slots in addition to the link…
Purpose ======= Improve the event slots feature and some other small improvements. Specification =========== Event form: - Add a "Slots" stat button to ease access to slots in addition to the link already present next to the multiple slots field. - Make "Sales Start" hidden by default for the event tickets. - Make sure the left column fields labels are correctly aligned with the title. A bottom margin was missing underneath the event image and was messing the form display. Slot views: - In calendar view, instead of restricting the creation of slots outside of the event time range, ask confirmation and adjust the event time range to include the new slots. - In list view, removing the editable bottom behavior which is messy and tricky to use from mobile. Instead opening the slot form in a dialog. This also now provides the timezone info to the user. - In calendar and list view, adding a "New" button to allow single event slot creation. - Add an hint for the user to make sure they understand that they need to select days in order to add multiple slots. - Changing the multi create "Add" button color to primary to make it more noticeable at first sight. - For the slots out of time range validation error. Format the event time range the same way as the slot time range so that it's easier to compare the 2. Task-5114075 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update enhances collaboration by displaying the current time and date in avatar cards and direct message headers, taking into account each user's timezone. This ensures users across different time zones see the time accurately, improving communication and workflow efficiency.
Original PR description
**Specifications:** • Display the current time and date in the avatar card using the timezone of the user only if the card user's timezone differs from the current user's. • Show the local time below the user name in the header of direct messages . **Purpose:** • Enhance cross-timezone collaboration by presenting the local time of other users during interactions task-4613148 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#210094
This update separates the granularity of time off requests from allocations, allowing accrual plans in hours to be taken in days when needed. This change enhances flexibility in managing employee time off, aligning with how accruals are currently handled. The update also includes related data and test updates.
Original PR description
Previously, the time off given to the employee (Accrued/Allocated) had the same granularity of that which the employee requests, for example the employee accrues hours in his plan and consequently can use this time off type in hours, or can only accrue days to time off types in days and half-days. This task separates the dependency between both so that accrual plans in hours can be taken only in days if needed task: 4596117 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects and enhances the data related to leave types within Odoo, ensuring accurate calculations and reporting. The changes, driven by a separation of time off given/taken, have been thoroughly tested to guarantee reliable leave management across various modules. This improves the overall accuracy of time off tracking.
Original PR description
Following the separation of granularity between time off given/taken, all leave types data is updated to correctly reflect the current settings task:4596117
This update streamlines how Odoo handles binary data (like images and files) by moving away from base64 encoding. This change improves performance and prepares Odoo for future changes in how binary data is stored in the cache, ultimately reducing data usage and simplifying the codebase.
Original PR description
`datas` is base64-encoded and we directly decode it once set. Most of code should use `raw` directly and avoid handling base64 encoded data, because in the future we will change the cache…
`datas` is base64-encoded and we directly decode it once set. Most of code should use `raw` directly and avoid handling base64 encoded data, because in the future we will change the cache representation to avoid handling encoded values. This PR simplifies current usages and will allow to change the representation of binary fields in cache (which are today base64 encoded). base64 takes more space and there is a lot of encoding/decoding involved depending on the abstraction layer, the end goal is to only handle raw data and encode only for the client. - In `odoo.tools.images` a few base64 functions are deprecated (one remaining for later). - Allow importing files (see convert) without going though base64. - Binary fields have now `convert_to_read` (encode as base64) and `convert_to_write` (use the cache format) defined. The *read format* is used by the client and should not be used in the models. - base tests define common data that can be reused. task-4251301 https://github.com/odoo/enterprise/pull/100997 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update enhances the HTML editor's undo/redo feature by grouping consecutive changes to the same text node into a single operation. This results in smoother and more reliable editing, preventing issues where multiple edits were not correctly reflected when undoing or redoing. It improves the overall user experience when making multiple edits within the HTML editor.
Original PR description
This commit undoes/redoes all consecutive steps that modify the same text node in a single call to `undo/redo()`. task-5155954
This update allows each company within an Odoo setup to define its own customer lead times for products. This ensures more accurate forecasting and planning across different business units, addressing inconsistencies in delivery timelines.
Original PR description
*= sale_stock In multi-company environments, different companies often operate with distinct delivery lead times, and these values may differ from one company to another. This enhancement allows each company to configure its own customer lead time on a product, ensuring clearer and more accurate planning across multi-company setups. Task - 5153210
This update allows each company within an Odoo setup to define its own customer lead time for products. This ensures more accurate sales forecasting and planning across multiple companies, aligning with recent community updates for smoother inter-company order flows.
Original PR description
In multi-company environments, different companies often operate with distinct delivery lead times, and these values may differ from one company to another. This change makes the sale_delay field company-specific. To align with recent community changes, the customer lead time is now computed based on the current company of the purchase order line, ensuring a smooth and consistent inter-company flow. This enhancement allows each company to configure its own customer lead time on a product, ensuring clearer and more accurate planning across multi-company setups. Task - 5153210
This update enhances the Thai version of Odoo by improving its accounting and tax settings. Specifically, the chart of accounts, tax templates, and asset configurations have been updated to ensure better compliance with Thai regulations and improve the user experience. This ensures accurate financial reporting for Thai businesses using Odoo.
Original PR description
Expanded and updated the Thai localization with an enhanced chart of accounts, updated tax templates, asset templates, and tax group configuration for better compliance and usability. Task-5395076 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#242520 Forward-Port-Of: odoo/odoo#240668
This pull request enhances the visual presentation and usability of the account reports module. Specifically, it updates the styling of review states, clarifies account status display, and introduces a redirect to the checks view for single returns, improving the overall user experience and report clarity.
Original PR description
task-5155703 Forward-Port-Of: odoo/enterprise#98675
1 change
Enhancements to existing features
This update adds crucial data attributes to Odoo's tax calculations and NFS-e submissions when the Brazilian fiscal reform is active. Specifically, it includes 'name,' 'businessName,' 'federalTaxId,' and 'type' fields, ensuring accurate tax reporting and compliance with new regulations. This change supports the ongoing requirements of the Brazilian tax system.
Original PR description
Purpose: Additional attributes are required to be sent in the rendered node for tax calculation and NFS-e submission when the fiscal reform is enabled. The additional required attributes are: - name - businessName - federalTaxId - type task-5450129 Forward-Port-Of: odoo/enterprise#103438
3 changes
Enhancements to existing features
This update modifies the chart of accounts for Odoo's Vietnamese localization to align with recent accounting regulations (Circular 99/2025). This change is necessary to ensure compliance with Vietnamese tax laws, taking effect in January 2026. It impacts financial reporting within the Odoo system for Vietnamese businesses.
Original PR description
Update the COA for the vietnamese localization, which is based on the circular 200/2014 by the new one based on the circular 99/2025. This new COA applies starting in Jan. 2026 task-5357470 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update enhances the longpolling controller by adding detailed logging and performance monitoring. These changes improve the stability and efficiency of the system, ensuring smoother operation and faster response times. This is a key improvement for overall system performance.
Original PR description
This PR adds logging and performance check for the longpolling controller Related PR for >= saas-18.3: https://github.com/odoo/odoo/pull/241467 Forward-Port-Of: odoo/odoo#241469
This update adds crucial data attributes to Odoo's tax calculations and NFS-e submissions when the Brazilian fiscal reform is active. Specifically, the system now includes 'name', 'businessName', 'federalTaxId', and 'type' fields, ensuring accurate tax reporting and compliance with new regulations. This change improves the reliability of Brazilian tax processing.
Original PR description
Purpose: Additional attributes are required to be sent in the rendered node for tax calculation and NFS-e submission when the fiscal reform is enabled. The additional required attributes are: - name - businessName - federalTaxId - type task-5450129 Forward-Port-Of: odoo/enterprise#103438
1 change
Enhancements to existing features
This update allows system administrators to customize the main Odoo home menu with a targeted message. Administrators can configure a new setting to display important information, such as planned maintenance, directly on the home screen. This provides a centralized way to communicate critical updates to users.
Original PR description
Display a message on home menu based on an ir.config_parameter that can be added directly in the database by the system administrator.
The ir.config_parameter is sysadmin.message and should be a json loadable. The format shoud be something like this:
{
"type": "warning",
"replace": false,
"warning_type": "user",
"message": "`<span>A maintenance operation is planned on your server on <strong>2026-01-15</strong> between 14h and 15h</span>`"
}
Forward-Port-Of: odoo/enterprise#102239