Daily updates from Odoo
Friday, June 19, 2026
8 changes · master
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 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 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 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