Daily updates from Odoo
Friday, June 13, 2025
13 changes
3 changes
Resolved issues and error corrections
Opening the VoIP contacts tab no longer fails when a contact has a phone number but no name. These unnamed contacts are now safely grouped at the end of the list under a "#" section, keeping the address book usable.
Original PR description
An error was arising when making the following steps: 1. create a company contact with a proper name. 2. create an invoice address for that company through the company form view. 3. set a phone number for the invoice. 4. leave the `name` empty. 5. open the contacts tab on VoIP. This happened because the code was trying to access the first charachater of a falsy string which is `voipName` in this case. A solution to this was to guard falsy names of contacts and add a section for contacts with empty string. This section will have a title of "#" and will appear at the end of the list.
The AI chat interface now places the copy button directly under the user's message instead of on the opposite side of the chat. AI action buttons are also better aligned with message bubbles, making chat actions clearer and easier to use.
Original PR description
This commit fixes the alignment of the copy button in ai chats for user messages. --- Behaviour Before this Fix --- The copy button would be aligned on the left side of the chat window while the user message would be on the right side. --- Changes Done for the Fix --- Previously, the flex-reversed class was added in the contentContainer div, which includes the message and its actions. That was removed and now the flex-row-reversed class is added when the chat is not AI. When the chat is AI, the flex-row-reversed class is added but this time only for the actions div. --- Behaviour After the Fix --- The copy button is now aligned on the right side, under the user's message. Task-4840542
Reconcile model names now display correctly in the accounting reconciliation widget even when users change their language. This prevents blank model names and avoids related widget errors, making reconciliation more reliable for multilingual users.
Original PR description
The name of the reconcile models displayed in the widget was sometimes empty due to a mismatch in user language. Specifically, if a reconcile model was created in one language (e.g., en_US) and the user switched to a different language, the model name would not be found and thus appear empty. This led to a props validation error in the widget. task-4863754
4 changes
Resolved issues and error corrections
This update improves the reliability of Web Studio's internal test environment by ensuring cleanup happens properly between tests. It helps prevent false test failures when custom models or fields are created, supporting more stable future development.
This fixes an internal test setup issue in the India payroll module by removing or correcting unused demo data. It helps keep automated checks reliable without changing day-to-day payroll functionality for users.
Employees can now choose the work entry source when Attendance is installed, not only when Planning is installed. This fixes an inconsistency so businesses using either app can configure how work entries are generated from the employee form.
Original PR description
…e having multiple options Bug / current behavior: The field work_entry_source was added to the employee form view only when installing hr_work_entry_planning (a dependency of the Planning app). Required behavior: The field work_entry_source should be shown upon installing hr_work_entry_attendance (a dependency of the Attendance app) as well. Both modules add a new selection to the field. Thus, when either module is installed, the field should be added to the form view to allow the user to choose. Fix: Add the field work_entry_source as invisible to the form view in the base module hr_work_entry. Make it visible once you install any of the planning or attendance modules. task-4866002 Community PR: https://github.com/odoo/odoo/pull/213982
Updates internal spreadsheet test coverage to match recent changes in pivot table behavior and highlight coloring. This helps keep automated checks reliable so spreadsheet features continue to work as expected without affecting day-to-day users.
Original PR description
See https://github.com/odoo/o-spreadsheet/pull/6414 Task: 4793572
6 changes
Resolved issues and error corrections
Fixes an issue where image transformation controls could stay visible after a user deleted an image in the editor. This prevents confusing leftover controls and keeps the editing experience consistent, including in Chrome.
Original PR description
### Steps to reproduce: - Insert an image into the editor. - Open the Transformation controls for the image. - Press the `Backspace` key to delete the image. - The transformation overlay remains…
### Steps to reproduce: - Insert an image into the editor. - Open the Transformation controls for the image. - Press the `Backspace` key to delete the image. - The transformation overlay remains visible after the image is removed. ### Description of the issue/feature this PR addresses: - In commit [1](https://github.com/odoo/odoo/commit/85698bf4f591fc9280f054b9a255a7d5ff4d1fe2), the `image_transform_button` component unmounted before `selectionchange` event could fire. As a result, event listener was removed, and the transform container was not closed when the image was deleted. Desired behavior after PR is merged: - The `selectionchange` listener is now attached within the `image_transformation` component. - A `keydown` listener is also added to explicitly handle Backspace and Delete keys, addressing the case where Chrome does not trigger `selectionchange` on image deletion. task-4831728 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Manufacturing worksheets will no longer allow videos in the description area when those videos cannot be shown in the Shop Floor interface. This prevents users from adding content that would later disappear, keeping shop floor instructions consistent and reliable.
Original PR description
Problem: Videos added in the operation worksheet are not visible on the Shop Floor interface. Cause: `embedded_components`, such as video iframes, are only supported within the HTML editor context and cannot be rendered elsewhere. This results in the video being silently dropped. Solution: Introduce a `disableVideo` flag for the `note` field in worksheet views. This avoids embedding unsupported video content and ensures the interface remains consistent. Steps to reproduce: 1. Go to Manufacturing > Operations > Worksheet. 2. Add a video in the worksheet's description field. 3. Create a Manufacturing Order (MO) for a product using this operation. 4. Confirm the MO and open it in the Shop Floor interface. 5. Open the worksheet tab. → The video is missing (not rendered). opw-4783722 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Studio exports no longer fail when a website uses a theme and the view has not been changed in Studio. This lets users complete exports reliably without needing to make unnecessary edits first.
Original PR description
**Before this commit:** - If the user had a website with a theme, then exporting from `Studio Export` would fail if no changes were made to the view via `web_studio`. **After this commit:** - The export now completes successfully, even when there are no changes made in the view through `web_studio`. task-4815179
This update corrects a test configuration problem in the Swedish point-of-sale localization that was causing automated validation to fail. It helps keep quality checks running reliably without changing business functionality for users.
Original PR description
In this commit: ------------ - We are fixing the unknown key "test" runbot error. runbot error-226611
This fix aligns the Italian point of sale tax calculation logic between the system backend and the browser interface. It helps avoid inconsistent tax rounding behavior during POS transactions, reducing the risk of incorrect totals or reporting differences.
Original PR description
rounding_method is there on the python code but not js-side.
The VIES summary report no longer crashes when integer rounding is enabled. This ensures users can open and review the report with rounded amounts as expected, improving reliability for tax reporting workflows.
Original PR description
When we enable the integer rounding option on this report, a traceback is raised at the report opening. It happens because integer rounding didn't support a groupby when a custom engine is used. opw-4688616