Daily updates from Odoo
Friday, June 19, 2026
17 changes
1 change
Enhancements to existing features
This update changes the unit of measure for the 'Flour' product in the Point of Sale system to kilograms. This adjustment is necessary to properly configure product weighing, particularly for compliance with the l10n_eu_iot_scale certification, ensuring accurate inventory tracking.
Original PR description
This small PR sets the "Flour" product's units of measure to kilograms. This helps to configure the weighing of the product, especially for the l10n_eu_iot_scale cert Forward-Port-Of: odoo/odoo#270508
1 change
Enhancements to existing features
This update incorporates support for the states of Tajikistan, Turkmenistan, Kyrgyzstan, Armenia, and Kazakhstan, aligning with international ISO 3166-2 standards. This change improves data accuracy and consistency by displaying state names instead of codes within address fields. This update is considered an improvement to the base system.
Original PR description
Added the states of Tajikistan, Turkmenistan, Kyrgyzstan, Armenian, and Kazakhstan to align with official ISO 3166-2 standards. In addition change their address format of the country to show state name instead of state code. task-6237707 task-6237595 task-6237473 task-6237440 task-6237284 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#269091
11 changes
Enhancements to existing features
This update significantly improves the user experience of the sign request control panel by redesigning the interface and modernizing the underlying technology. The changes include a cleaner, more intuitive design, improved responsiveness, and a more efficient architecture for managing sign requests, resulting in a better user experience and streamlined workflow.
Original PR description
### Context The previous signer status header in the sign app relied on static QWeb injected from the backend and legacy DOM manipulation (jQuery/Vanilla JS) to handle state changes like "Resend"…
### Context The previous signer status header in the sign app relied on static QWeb injected from the backend and legacy DOM manipulation (jQuery/Vanilla JS) to handle state changes like "Resend" buttons. Additionally, the horizontal layout consumed too much screen space for documents with multiple signers, and users lacked quick visual context of the document's template tags. ### Summary of Changes This PR completely modernizes the Sign Request Control Panel header, moving it to a pure OWL architecture while vastly improving the UI/UX. 1. Architectural Refactoring (Legacy JS to OWL) Extracted the signer status wrapper into a modern, reusable OWL public component (SignerStatusBadge) that works flawlessly in both the backend and the portal. Ripped out fragile querySelector DOM manipulation for the "Resend" buttons. Button state (e.g., swapping a paper-plane icon for a success checkmark upon clicking) is now fully managed via reactive OWL state and clean RPC calls. 2. UI/UX Redesign Redesigned the signer list into a compact, native Odoo <Dropdown> when multiple signers are present, saving valuable horizontal space. Replaced bulky text buttons with clean, semantic Bootstrap/FontAwesome icons (check/clock/cross for status, paper-plane for actions) for a more modern SaaS feel. 3. Added Template Context Reused the existing SignTemplateHeaderTags component to display the original template's tags directly in the request control panel (in read-only mode). It gracefully hides itself if no tags or template exist. Task: 6109365
This update enhances Odoo's payment processing by tailoring it to the specific requirements of our key delivery partners like Shiprocket and Ups. This change allows for more accurate and reliable payments, streamlining the integration with these important services and improving overall transaction management. It’s a crucial step in supporting our growing delivery network.
Original PR description
See also: - https://github.com/odoo/odoo/pull/258854 - https://github.com/odoo/documentation/pull/18527
This update correctly classifies the Company Executive's meal voucher as a benefit, aligning with payroll best practices. Previously, it was treated as a salary input, which has now been corrected. This change ensures accurate reporting and compliance.
Original PR description
The meal voucher for the Company Executive is a salary input and should be a benefit. Task: 6303114
This update allows Field Service technicians to directly include subscription products with 'Accept One-Time' enabled within the Field Service product catalog during on-site visits. Previously, these subscriptions required a separate 'Extra Quotation' process. This streamlines the sales process and improves technician efficiency.
Original PR description
This commit makes subscription products with the "Accept One-Time" option enabled visible in the Field Service product catalog, so technicians can add them as one-time sales during on-site interventions without going through the Extra Quotation flow. task-5401135
This update enhances the task planning process within the Gantt view by adding a helper that prevents empty dialogs when creating new tasks. This improves the user experience and reduces potential confusion for users adding tasks from the Gantt chart.
Original PR description
This commit adds a custom no-content helper to the dialog opened when planning tasks from the Gantt view. task-3613715
This pull request simplifies the process of configuring car options for employees within the salary offer and employee view. The changes focus on improving the user experience, making it easier for HR to manage car-related benefits and for employees to select their preferred vehicle options. This enhances efficiency and clarity in the contract creation process.
Original PR description
-Introducing some UX changes in salary configurator and employee's offer view to simplify car options.
This update allows users to specify quantities and units for sections within subscription orders. Changes to these values are now accurately reflected in both the generated PDF reports and the customer portal, providing more precise order information. This enhancement improves transparency and accuracy for subscription management.
Original PR description
In the community PR, users can set the quantity and unit on sections and subsections. When a user changes the quantity or unit, these values are displayed on the generated PDF and in the portal. To support this, we changed the table architecture to keep it consistent in sale_subscription. PR: https://github.com/odoo/odoo/pull/267933 Upgrade: https://github.com/odoo/upgrade/pull/10417 task-6075605
This update enhances the user experience for managing shifts within Odoo, particularly in the planning and portal sections. Key changes include direct sign-in and completion buttons on the planning kanban view, a simplified portal interface, and improved navigation for mobile users. These improvements streamline shift management workflows and boost operational efficiency.
Original PR description
_*= planning_field_service,project_forecast,planning_field_service_sale_timesheet,
sale_planning
- Add a Sign Report button to allow users to sign reports directly from planning shifts
- Improve the planning kanban UI by adding Sign In and Complete buttons,
allowing users to directly sign in and complete shifts from the kanban view
- Enhance the portal view by hiding breadcrumbs, banners, and print button in sign mode
- Add a back-to-shift navigation button in the portal
- Improve the mobile view of the shift form view
task-6218179This change addresses a requirement from Avalara, who need the LC16 code to be dotted for their city web services. Previously, Odoo automatically removed these dots. Now, the LC16 code is sent with the dots, allowing Avalara's tool to correctly sanitize the data.
Original PR description
Purpose: Avalara requires the LC116 code to be dotted for certain city webservices. Their tool will automatically sanitize the dots for cities that don't support it. Current Behavior: Odoo sanitizes the LC116 code before sending the JSON payload. Expected Behavior: The LC116 code is sent in the JSON payload with the dots. task-6304351 Forward-Port-Of: odoo/enterprise#120648
This update enhances navigation between sold assets and related customer invoices. Now, invoices linked to a sold asset are directly accessible from the asset's record, and vice versa, streamlining workflows for sales and accounting teams. This improves visibility and efficiency in managing related transactions.
Original PR description
This commit improves the navigation from a sold asset to the customer invoice and vice versa. A reference link of the sold asset is added to the chatter of each invoice used in sale. Also, all invoices used in sale are added as reference link to the asset's chatter. task-4413649 Forward-Port-Of: odoo/enterprise#118665
This update allows users to connect their personal LinkedIn accounts and schedule posts to Facebook and Instagram Stories. It also includes several UX improvements to make the social posting experience easier and more intuitive.
Original PR description
Purpose ======= This PR addresses many improvements in the social app, the two main ones being allowing to link your personal LinkedIn account and to post Facebook and Instagram "Stories". We also…
Purpose ======= This PR addresses many improvements in the social app, the two main ones being allowing to link your personal LinkedIn account and to post Facebook and Instagram "Stories". We also made a lot of UX tweaks along the way to make the social app easier to use, with a bit of much needed polish as the app has not been worked on a lot since it was introduced (about 7 years before this PR). Specifications =========== Allow the users to add their personal LinkedIn account in Social (and not only the page for which they are admin), and to post on them. During the authentication process of Social, if something went wrong we need to manually go back or enter the Odoo database URL to retry. It can be very frustrating, and so now we open the authentication URL in a new window, and when the process is done we close the window and refresh the view. Show a loading page while doing the token exchange process (which can take some time depending on the number of pages). Allow removing the accounts from the "Connect Account" modal. Show the icons of the selected medias in the calendar view. Improve the way we schedule posts. Allow the users to comment their own posts right after posting. Allow posting stories on Facebook and Instagram. Allow sorting the image when posting on a social media. Use AI to write social post. Show the chars count for all medias while typing the message. Improve the computation of the tweet length (URL must count for 23 chars and emoji for 2). In the post form view, show the media icon instead of the media name when selecting the accounts. Do some refactoring to unify the name for the social post message field. Schedule the social post with a modal, like it's done in mass-mailing. (see each individual commits for more details) Task-5491124
1 change
Enhancements to existing features
This update enhances the system's ability to process payments through Powens and Saltedge by adding debtor and creditor information to the data sent to our payment processor. This change ensures accurate payment initiation and improved integration with payment gateways.
Original PR description
In order to be able to initiate payments using Powens and Saltedge, we need to include debtor information in the payload sent to Odoofin. This commit adds the necessary fields and updates the tests accordingly. Task ID: 5977148, 6095729 Forward-Port-Of: odoo/enterprise#119843
2 changes
Enhancements to existing features
This update simplifies how the account_edi_ubl_cii report templates are identified, reducing potential conflicts with other Odoo modules. Previously, a fragile inheritance method caused issues when updating templates. This change creates a more reliable and stable system for identifying the necessary updates.
Original PR description
**Description of the issue/feature this PR addresses:** As the new `xpath` is expecting a very specific type of `t-if` which is possibly changed in other templates of third parties or even Odoo itself which do not depend on this module, we take a more robust approach to identify the block **Current behavior before PR:** Issues with inherited views outside the dependency tree (because of primary=True) **Desired behavior after PR is merged:** Less friction and smoother identifier of the needed diff Info: @wt-io-it --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update enhances the error messages related to leave validity, particularly when creating public holidays. The improved message will significantly help customers and our support team quickly identify and resolve leave allocation problems, reducing troubleshooting time. This change improves the user experience and support efficiency.
Original PR description
The current message is pretty useless as of now when a lot of leaves are being written to, notably when creating a public holiday, which sets the state of all the leaves overlapping the public holiday's day to be reevaluated, and if an error occurs, you have to go through every employee's leave allocation and leaves taken to hopefully find one who might have to many days taken/not enough allocated. This extra information will be a huge QOL improvement, for the customer who will be able to troubleshoot his issue himself more easily, but also for our support team as the only way to debug those kind of issues now is to put a breakpoint there and see what employee has an issue. opw-4411999 Forward-Port-Of: odoo/odoo#200376
1 change
Enhancements to existing features
This update enhances the Speedscope profiling feature by adding a control panel to manage rendering options. Previously, Speedscope visualizations were static and prone to performance issues. Now, users can easily enable or disable options, leading to faster, more reliable results and simplified sharing of profile data.
Original PR description
This pr aims to improve the profiling, and mainly speedscope rendering experience. Right now, visualizing a speedscope result: Gives a static result. The makes the usage of some options like constant time impossible without editing the code. It also generate to much different types of output at the same time making it slow and leads faster to memory error. Needs to enable the profiling on the database to be able to visualize the result. This can be painful mainly when trying to access result after some time, or just after profiling in python. This pr removes the need to enable the profiling to visualize the results. This pr adds a wizard to enable or disable some options. As a bonus it is now possible to combine multiple profile in the same view (experimental) Backport of https://github.com/odoo/odoo/pull/189370 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr