Tuesday, March 17, 2026
29 changes · saas-19.1
Resolved issues and error corrections
This update resolves a bug that prevented the burndown chart in the Project app from loading correctly in sample mode when no project was selected. The change ensures the necessary context is set, preventing errors and improving chart functionality. This fix aligns with best practices for embedded actions.
Original PR description
The burndown chart embedded actions use action_id which bypasses the Python method that sets required context (stage_name_and_sequence_per_id). Without this context, the JS model makes RPC calls that fail in sample mode when no project record is selected. This change replaces action_id with python_method, following the same pattern used by hr_timesheet for similar embedded actions. Steps to reproduce: 1. Open Project app 2. Access burndown chart via embedded action without records 3. Sample mode triggers the crash Current behavior: TypeError reading undefined field type Expected behavior: Burndown chart loads with proper context task-5347524 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes a potential error that could occur when a session record doesn't have associated device information. It guarantees that session records always contain necessary data like IP address and user agent, preventing errors during user activity tracking. This improves data reliability for reporting and analytics.
Original PR description
This commit ensures that there is always information linked to a `res.session` record. This causes an error, for example, if `user_agent` is `False`: ```py ... =…
This commit ensures that there is always information linked to a `res.session` record. This causes an error, for example, if `user_agent` is `False`: ```py ... = self.__user_agent_parser(device.user_agent) ``` We ensure that if we have a `is_current` `res.session` record which does not have a `is_current` `res.device`, we have information (`ip_address`, `user_agent`, `country`, `city`). Scenario: - device A detected at time T0: info A in session + new log A - device B detected at time T1: info B in session + new log B - log B is unlink (or marked as revoked) - device B detected at time T2: nothing ==> `web_read` on `res_users` ==> error T2 < T1 + `DEVICE_ACTIVITY_UPDATE_FREQUENCY` - device B detected at time T3: info B updated in session + new log B T3 > T1 + `DEVICE_ACTIVITY_UPDATE_FREQUENCY` Explanation: At this moment, T2, because log A exists, a `res.session` record exists. When we compute information for the `res.session` record, as this record is the current session, we must get the current device. To retrieve the current device, we use the `res.device` model. Unfortunately, no current device is present (because log B has been deleted) and `DEVICE_ACTIVITY_UPDATE_FREQUENCY` has not been exceeded. In this case, we have a current session without current device. Note: However, we are certain that there is at least one device for this session record because session records are built with device records. Task-6023651
This pull request reverts a previous change that was causing issues with email notifications related to HR contracts. The fix addresses a technical problem that was preventing proper email delivery, ensuring that users receive expected notifications regarding contract updates. This change improves the reliability of the HR contract management process.
Original PR description
Revert https://github.com/odoo/enterprise/pull/106974
A technical error in the Point of Sale app's order form was causing a problem with displaying product information. This update removed a problematic widget that was relying on a field not present in the order data, resolving the error and ensuring proper order form functionality. This change improves the stability of the Point of Sale module.
Original PR description
Steps to reproduce: = - Open the `Point of Sale` app in the backend. - Open the order list view and try to open any order. Issue: = - A traceback is raised: `KeyError: 'translated_product_name'`. Reason: = - The `product_label_section_and_note_field` widget introduced a dependency on the `translated_product_name` field, which is not present in `pos.order.line`. Fix: = - Removed the widget `product_label_section_and_note_field` from pos order form view as it is not required in pos. Reference PR: = - https://github.com/odoo/odoo/pull/248401 task-6040210 Forward-Port-Of: odoo/odoo#254108
This update corrects a display issue in the employee emergency contact section. Previously, the 'Relationship' field was incorrectly shown for all employees, regardless of their company location. Now, the field is hidden for employees associated with non-Indian companies, ensuring accurate data presentation.
Original PR description
### Steps to reproduce: - Install l10n_in_hr_payroll. - Create an employee (also link a user) in an Indian company and another company. - Go to My Profile > Private Information > Emergency. - The Relationship field is shown for non-Indian employees as well as employees from other countries. ### Issue: - We're not hiding the relationship field if employee is from other country . ### Fix: - We'll hide this field if an employee belongs to non-indian company. Task: 6008888 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#254162
This update corrects a bug where resending invoices to MER would overwrite existing addendums, even if the invoice hadn't been sent. The fix ensures that existing addendums are updated instead of being replaced, streamlining the invoice processing workflow and preventing data loss. This improves the reliability of invoice handling.
Original PR description
Issue: when resending an invoice already sent to MER, the existing addendum is overwritten even when the invoice is not sent to MER. Solution: updating values on the existing addendum rather than creating a new one, if it already exists. task-none --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#253730 Forward-Port-Of: odoo/odoo#253281
This update fixes a technical problem where Chrome was creating unnecessary temporary files, leading to potential performance issues. By directing Chrome to use its temporary directory as its data directory, we now automatically clean up these files during the system's regular cleanup process. This ensures smoother operation and prevents file clutter.
Original PR description
It's unclear since when or under what configuration exactly, but Chrome(ium?) seems prone to creating directories called `org.chromium.Chromium.*` (or some variant thereof) in the temp dir (some people report them to be prefixed by a `.`) and never clean them. By telling chromium that its tempdir is its data dir, it creates its litter in there, and we remove the entire thing during cleanup, solving the littering. Forward-Port-Of: odoo/odoo#253350
This update fixes a minor issue where closing the emoji or GIF picker resulted in it not reopening immediately. The change ensures the picker state is correctly reset, providing a smoother and more reliable user experience when selecting emojis or GIFs. This prevents users from needing to click multiple times to access these features.
Original PR description
**Current behavior before PR:** When the GIF or emoji picker is dismissed by clicking outside, the component state remains out of sync because `props.onClose` isn't triggered. This causes the next attempt to open the picker to fail, requiring an extra click from the user. **Desired behavior after PR is merged:** Closing the picker now correctly triggers the `props.onClose`. This ensures the component state is always reset, allowing the picker to reopen immediately on the next click. task-[5953015](https://www.odoo.com/odoo/project/1519/tasks/5953015) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#253776 Forward-Port-Of: odoo/odoo#250630
This update corrects a bug that was preventing accurate calculations for salary percentages within the HR contract module. The fix ensures that benefit amounts are correctly calculated based on percentage values, improving the reliability of payroll data. This resolves a minor issue impacting HR reporting.
This update resolves an issue where default values for selection-type salary inputs weren't correctly displayed in payslips. The fix ensures that the form view updates properly when new inputs are added, guaranteeing accurate and consistent salary calculations. This improves the reliability of payroll processing.
Original PR description
Steps to reproduce: - Create a Salary Input of type 'selection'. - Assign a default value to this input. - Add the input to a payslip. Bug Cause: The form view is not re-comupting the values when it's assigned for the first time since the container is not changed Solution: Forcefully update the payroll_properties when we add new inputs in the payslip form task-5357904
This update reverts a recent change related to the Eco Voucher benefit within the Belgian HR payroll module. This change was causing issues with payroll calculations and has been rolled back to ensure accurate and compliant payroll processing. The change ensures continued compliance with Belgian tax regulations.
This update fixes an issue where the website's filter options disappeared when using the 'off-screen menu' style. The change ensures the filter button remains visible when no sort or pricelist options are selected, providing a consistent and user-friendly experience. This improves the usability of product searches on the website.
Original PR description
Versions -------- - 19.1+ Steps ----- 1. Disable all pricelists to hide pricelist filter 2. Go to shop page 3. Change Filters style to "Off-screen Menu" - Note that a "Filters" button appears next to the sort by dropdown 4. Remove the sort by from the toolbar by untoggling it Issue ----- When the filters are set to off-screen and there is no sort by dropdown or pricelist dropdown, the filters button disappears. Cause ----- The div containing the filters button, sort by dropdown, and pricelist dropdown, is set to `d-lg-none` when there is no pricelist dropdown and no sort by dropdown, causing it do disappear. Solution -------- Only allow the div to disappear when the filter button shouldn't appear (`wsale_has_filters_btn` set to False) opw-5933858
This update resolves an issue where mass email sorting failed due to inconsistent date information in emails. The fix adds a default date of midnight to emails without a defined date, ensuring consistent sorting and preventing errors during email processing. This improves the reliability of email sending operations.
Original PR description
Background: In odoo.com, due to some migration scripts, there are messages without neither a date nor create_date Issue: When sending mass emails to applicants, when determining the parent email, emails are sorted using their date, but since some emails have a date and some don't, comparing them results in an exception (comparing datetime with bool). Fix: Add datetime.min as a fallback for the email's date if neither date nor create_date are set. Task-6041584
This update resolves a display issue in the 'By Employee' time off reporting feature. Previously, users only saw record IDs in the list view; now, the report correctly shows relevant employee data. This ensures accurate reporting and simplifies data analysis for HR teams.
Original PR description
**Steps to reproduce** - Go to Time Off > Reporting > By Employee - Switch to graph view - Click on one of the columns Issue: only the id of the records is displayed in the list view **Cause** There's no list view defined for the `hr.leave.employee.report` Issue present since the rework in 1c3f5633ef87f6d9c5a6169eefd51cd42ef442d5 opw-5977793
This update resolves a mobile UX issue where incorrect time off balances were displayed and leave types without maximum limits lacked the 'Available' label. This ensures employees see accurate time off information when using the mobile app, improving usability and reducing potential confusion.
Original PR description
This change fixes 2 problems in the mobile UX side panel: - Time off types with zero allocations were shown. - Leave types without a max leave amount didn't show the "Available” label. task-6030539 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes an issue where the 'Edit Menu' button within the link preview was overlapping its text. The change ensures all buttons in the preview display correctly, providing a cleaner and more professional user experience. This improves the overall usability of the HTML editor module.
Original PR description
Before this commit: the Edit Menu button's text stacks when the url's preview is loaded. After this commit: we make sure the button isn't wrapped for all the buttons inside the link preview. task-6036771 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update ensures that CTA queries use the current day's currency rate, rather than a rate from the previous day. This correction improves the accuracy of currency calculations within the system, leading to more reliable reporting and financial data. It addresses a previous issue where outdated rates were being used.
Original PR description
We use currency rate at day x - 1 to be applicable at a date x, which shouldn't be applicable in the cta queries. Use same-day rate for the CTA query. task-5969168 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects a technical issue where changes to contract salary information within the Odoo configurator were not consistently reflected. The fix ensures that all salary-related fields are accurately updated, providing greater control and precision for managing employee compensation. This improves data integrity and reporting accuracy.
This update fixes a technical issue that caused tracebacks when users attempted to insert AI-generated content into knowledge articles via the AI chat quick action. The fix ensures the correct function is passed during AI chat initiation, preventing errors and improving the user experience. This enhancement ensures smooth AI content integration within the knowledge base.
Original PR description
Prior to this fix, the user would get a traceback when trying to insert AI generated content to a knowledge article (IF they opened the AI chat through the quick action button in "New Article"). The traceback was shown because `selectPreviousInsertion`` function was not passed to the `aiSpecialActions`` object when calling the `launchAIChat` function. This function allows us to replace previously inserted content if the user choose to from the same AI conversation. When launching the AI chat from this quick action button, we can be sure that the article doesn't have any content previously inserted, so we can define the passed function but leave it empty. Task-5490199
This update resolves an issue where adding attributes to archived product templates caused errors. The change now correctly accounts for both active and archived product variants, preventing template deletion and ensuring archived templates retain their attributes.
Original PR description
When adding attributes to an archived product template, an error was raised because the template was incorrectly deleted. This happened because variant counting only considered active variants. Now counts all variants (active and archived) to prevent template deletion, and filters variants before activation to keep them archived when their template is archived. @qrtl QT6449 Forward-Port-Of: odoo/odoo#252927
This update resolves an issue where users were unable to correctly set both a start and end date for a date range field within the web_studio. The system now prevents setting both fields simultaneously, ensuring data integrity and a consistent user experience. This change improves the reliability of date-based configurations.
Original PR description
Steps to reproduce ================== - Install project,web_studio - Click on the three dots in the top right of a project - Click on settings - Open studio - Add a new date field - Set the start date field to Start date - Set the end date field to Expiration Date - Exit studio => The date range field is marked as invalid (red outline) Cause of the issue ================== https://github.com/odoo/odoo/blob/ee15163fe516817da277760752892ea76a699e22/addons/web/static/src/views/fields/datetime/datetime_field.js#L371-L373 We cannot set both the start and end field at the same time. opw-5403670 Forward-Port-Of: odoo/enterprise#110212 Forward-Port-Of: odoo/enterprise#108562
This update fixes a bug that prevented users from removing external members with edit access from spreadsheets after archiving. The fix updates validation logic to correctly handle both adding and removing access rights, resolving three related warnings and ensuring proper spreadsheet functionality. This improves the user experience and data management.
Original PR description
Problem: A bug occurs when an internal user with "Edit" rights to a spreadsheet is archived. Upon archiving, the user transitions to an external user, a state where "Edit" rights are strictly…
Problem: A bug occurs when an internal user with "Edit" rights to a spreadsheet is archived. Upon archiving, the user transitions to an external user, a state where "Edit" rights are strictly prohibited. However, due to a validation error in the access rights wizard, users were unable to fix this. Cause: The validation logic in `documents_sharing.py` performed checks after any action was taken. If an illegal configuration was detected, it set a flag to hide the Save button. Because the check did not distinguish between adding an illegal rule and deleting one, users were blocked from removing the very records causing the validation failure. Solution: The validation checks have been updated to account for the operation- type (addition or deletion). This ensures that while new illegal rules are still blocked, existing illegal rules can be successfully removed to restore the system to a valid state. A test was also added to prevent this problem form happening in the future. This PR applies uses the solution to fix the state of 3 warnings, ensuring they are only displayed when actually relevant. Specifically, it covers: - The warning triggered when removing external users with edit access in `documents_spreadsheets`. - The `has_warning_no_access` warning in documents. - The `has_warning_link_with_more_rights` warning. task-5902391 Forward-Port-Of: odoo/enterprise#108140
This update resolves issues with the formatting of Dutch SBR and ICP reports, specifically correcting incorrect VAT identifiers and date formats within the exported XML files. A cleanup process has been added to improve the readability of these reports for users.
Original PR description
Descriptions of the issues this commit addresses: The xbrli:identifier tags in the exported sbr and sbr icp files are wrong. They should always contain the company's vat without country code . The DateTimeCreation tag currently shows a date in a wrong format. It it YYYYMMDDhhmm but should be YYYY-MM-DDThh:mm:ss. Also the outputted xml is weirdly indented with many whitespaces and it makes it hard to read for no reason. --- Desired behavior after the commit is merged: This commit changes the values in the exported file to address those issues and adds the use of a cleanup helper to make the file human readable. --- task-5998939 Forward-Port-Of: odoo/enterprise#109359
This update simplifies the scatter plot chart by removing the unnecessary zoom feature, which created inconsistencies across axes. This change aligns with upcoming plans to allow users to manually set axis minimum and maximum values, providing greater control over chart presentation.
Original PR description
## Task Description This PR aims to remove the zoomable feature for the scatter plot, as it's kind of non-sense to be able to zoom on an axis and not on the other for this type of chart. Moreover, we will soon be able to manually set the min/max of each axis manually (in master). ## Related Task/PR - Task: 5388389 - [https://github.com/odoo/enterprise/pull/106189](https://github.com/odoo/enterprise/pull/106189) Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#246954
This update removes a confusing zoom feature from the scatter plot chart in Odoo Enterprise. This change simplifies the chart's functionality and aligns with upcoming plans to allow users to manually adjust axis ranges. This improves the overall user experience for this chart type.
Original PR description
## Task Description This PR aims to remove the zoomable feature for the scatter plot, as it's kind of non-sense to be able to zoom on an axis and not on the other for this type of chart. Moreover, we will soon be able to manually set the min/max of each axis manually (in master). ## Related Task - Task: 5388389 Forward-Port-Of: odoo/enterprise#106189
A test within the Odoo Enterprise system was failing when the 'Accountant' module wasn't present. This update corrects a discrepancy in the expected account used during testing, ensuring the test now runs successfully regardless of the 'Accountant' module's installation status. This resolves a minor technical issue that could have prevented future testing.
Original PR description
Currently test_bank_rec_widget_batch_foreign_currency_journal_without_entries fails when `accountant` module is not installed because the expected account differs opw-5887218 Forward-Port-Of: odoo/enterprise#110917
This update resolves a technical limitation in the Odoo Report Editor, preventing users from applying properties to fields selected within the '/field' command. Previously, this was not supported, leading to inconsistencies. This change ensures correct functionality and data handling within reports.
Original PR description
Properties are not supported in ir.qweb but only as t-out, while t-field doesn't support them. For this reason and the fact that properties have a path the model field selector barely handles we do not allow those field to be selected in the /field command task-5999790 Forward-Port-Of: odoo/enterprise#110409 Forward-Port-Of: odoo/enterprise#109486
This update fixes an issue where the lower portion of the barcode editing page was hidden by buttons. The change ensures that all fields are always visible, regardless of button size or zoom level, improving the user experience when adding or editing barcode items. This prevents frustration and ensures accurate data entry.
Original PR description
# How to reproduce - Set the barcode of a product - Go to Barcode > Operations > (Select any operation) > New - Click on the cog in the top right and type in the barcode you set for the product - Apply and then edit the item you added - Add options to the page (like Expiration Date) or increase the browser's zoom until the list of fields take the whole page # The problem The fields at the bottom of the page are hidden behind the buttons at the bottom # Why The controls at the bottom are positioned absolutely and with a high z-index, so they hide anything behind them. The form css class fixes this issue by adding a margin-bottom roughly the size of the controls. But this fix does not take into account the fact that the controls can grow in size when the DELETE button is displayed opw-5907564 Forward-Port-Of: odoo/enterprise#107496
This update removes birthday events from automatic synchronization with Google Calendar. These events are complex to manage and don't provide much value, often creating confusion for users. Filtering them out simplifies the calendar sync process and improves user experience.
Original PR description
Birthday events are a special kind of yearly-recurrent event that notably cannot be simply deleted like other events. They also appear as a separate calendar in the google UI to an extent, similar to tasks. As they require special handling, have little functional value and can be confusing due to that "fake calendar" behavior. We will now always filter them out of broad calendar sync. task-5966907 Forward-Port-Of: odoo/odoo#250916