Daily updates from Odoo
Thursday, June 18, 2026
27 changes · master
Resolved issues and error corrections
This update expands the functionality of the sign creation process by enabling drag-and-drop support for all pointer types – including touch and pen – on Odoo Enterprise. This allows users to more easily create, move, and interact with sign elements, improving usability across different devices and workflows.
Original PR description
Dragging sign elements was previously limited to mouse input. This fix ensures full support for all pointer types, including touch and pen, allowing users to drag new sign items, reposition existing ones, and interact with the interface seamlessly. task-5001223
This update ensures that all conversation history and attachments are correctly transferred when converting between Helpdesk tickets and Project tasks. Previously, this information was lost during the conversion process, which is now resolved to provide a more complete and accurate record of project communications and files. This enhances collaboration and data integrity.
Original PR description
Before this commit, attachments and chatter messages were not moved to the new record when converting a Helpdesk ticket to a Project task or a task back to a ticket. This commit ensures that: - The chatter history is transferred to the newly created record. - All attachments linked to the original record are moved to the new one. task-4796664
This update fixes a problem where the Timesheet Assistant was suggesting activities that were already tracked. Now, explicit timer sessions act as 'clipping masks,' ensuring tracked time takes priority. Additionally, the system now automatically updates its data to prevent issues when timesheets are deleted, improving overall accuracy.
Original PR description
The Assistant previously suggested activities for periods already covered by the physical timer. To fix this, explicit timer sessions now act as invisible clipping masks that prioritize tracked time over suggestions. This was implemented fully client-side because live timer interactions are inherently managed there. These local blockouts are merged into the timeline first to naturally clip overlapping events, but are hidden from the UI to prevent redundant cards. Finally, to prevent orphaned blockouts when timesheets are deleted, the cache self-heals by validating its IDs against the database on load instead. Task: 6216903
This update fixes an issue where documents added through the 'Add from Documents' feature didn't display correctly in emails. It now aligns with the standard email attachment flow, eliminating incorrect spacing and ensuring previews are shown, leading to a better user experience when sending documents via email.
Original PR description
**Purpose of this PR:** Before this commit, documents added via "Add from Documents" did not integrate properly with the mail composer: previews were not shown, and when a document was added as a link with an empty body, line breaks were still applied and introduced extra spacing above the attachment. This commit aligns added documents with the regular mail attachment flow so they render correctly in the composer, and avoids inserting unnecessary spacing when no text content is present. Related PR: https://github.com/odoo/odoo/pull/256866 task-5947683
This update ensures that employees are only paid for the actual hours they worked by correctly deducting undertime from their payslips. Previously, the system didn't automatically apply these deductions. The update also removed outdated test cases related to old company-level settings.
Original PR description
Previously, when an employee worked fewer hours than expected, the missing hours (undertime) were correctly tracked but the salary deduction was not applied on the payslip. After this improvement: - Undertime hours are now correctly deducted from the payslip so the employee is only paid for the hours they actually worked. - Removed test cases that were testing old company-level tolerance settings which have been removed. task-5892244
This update fixes a reporting issue where tax information wasn't correctly captured for invoices using group taxes in the Philippines. The change ensures that all child tax tags are included in generic reports, accurately reflecting tax details for SC/PWD exempt components and other tax categories.
Original PR description
When using group taxes, the base invoice lines only store the parent tax in the `account_move_line_account_tax_rel` table. Because of this, if a child tax within the group contains a specific tax report tag (e.g., tag 33A on the SC/PWD exempt component introduced in the base localization), the generic report query would previously fail to pick up those base lines. This commit updates the SQL join conditions in `l10n_ph_generic_report.py` to also match `account_tax.id` against the child taxes of the linked parent tax using the `account_tax_filiation_rel` table. This ensures that base lines are correctly reported under the tags of their respective child taxes. Task-6032306 See: odoo/odoo#269250
This update fixes a minor issue in the demo data for the Odoo Enterprise HR payroll module. Specifically, a reference to an employee type was incorrect, preventing demo records for non-permanent employees from functioning properly. This change ensures the demo data accurately reflects the system's configuration.
Original PR description
The non-permanent employee demo records referenced a missing XML id l10n_id_contract_type_non_permanent for employee_type_id. Point them at the actual record, l10n_id_employee_type_non_permanent. task-6215687
This update fixes a problem where users couldn't access payslips related to departing employees. The changes ensure that only the departing employee's payslips are displayed, preventing errors and improving the user experience. A technical update was also made to ensure compatibility with newer Odoo versions.
Original PR description
Bug 1: In the departure tab of the Employee, you can't open the payslip list Fix: Added a check to get the correct departure id depending on the model we are in Bug 2: You can select payslips for…
Bug 1: In the departure tab of the Employee, you can't open the payslip list Fix: Added a check to get the correct departure id depending on the model we are in Bug 2: You can select payslips for other employees than the departing employee and the payslips list is not affected Fix: - made fields `l10n_be_payslip_n_ids` and `l10n_be_payslip_n1_ids` stored and added a domain on them to only show the payslips of the departing employee - when a payslip is validated for the departing employee after creating the departure, it's added to the corresponding field Bug 3: You get an error because you can't read `currency_id` when opening n payslips (happens when the monetary fields are shown in the list) Fix: moved the `currency_id` to be inside the list instead of the parent form Note: the relation names for `l10n_be_payslip_n_ids` and `l10n_be_payslip_n1_ids` are changed to avoid upgrade error `m2m relations have respawn` as they existed before 19.2 in the removed `hr.departure.wizard` model. task-id: 6265648
This update resolves an issue where the project ID field was incorrectly marked as optional in the timesheet view. The system now correctly enforces the requirement for a project ID, ensuring accurate timesheet tracking and reporting. This change improves data integrity within the Enterprise module.
Original PR description
`project_id` is always required in the parent timesheet view. Setting it to `optional="hide"` in this inherited view is invalid. task-6113642
This update ensures that staff members, designated as part of an appointment type, are automatically added as attendees to new appointments created through the Gantt view. Previously, this step was manual. This change improves the user experience by streamlining appointment creation and ensuring staff are always included.
Original PR description
### Steps to reproduce: - Install 'Appointment' app - Configure an Appointment Type with your user as staff member - Go to the Appointments Gantt view - Click on the 'New' button to create a new…
### Steps to reproduce: - Install 'Appointment' app - Configure an Appointment Type with your user as staff member - Go to the Appointments Gantt view - Click on the 'New' button to create a new appointment > The staff member is not automatically added to the meeting's attendees (guests) list. ### Cause of Issue: When generating the default values for a new calendar event from the Gantt view (indicated by `booking_gantt_create_record` in the context), the base `default_get` method doesn't account for auto-adding staff members in obvious cases (when there's only one staff member available or the current user is one of the staff). ### Fix: Override `default_get` in `calendar.event` to automatically add these staff members when they are the only available option, providing a smarter and more seamless UX. opw-6181794 Note: the same PR was done for 18.0, but now this is moving it to master since it's more of a feature not a fix. Original PR: https://github.com/odoo/enterprise/pull/118331
This update improves the clarity of payslip reports by ensuring all line rates are consistently displayed with two decimal places. Previously, trailing zeros were shown, which was visually confusing. This change provides a more professional and accurate representation of employee compensation.
Original PR description
Problem: A lot of trailing zeros were displayed on the rate of each payslip line, in the salary tab of the payslip form. Solution: At first, it was decided to remove trailing zeros. But in the end, we chose to always display 2 decimal places. Task-6310227
This update resolves an issue where the appointment calendar displayed 'no available slots' for future months when appointment scheduling lead times were long. The fix accounts for lead times to ensure the calendar accurately reflects available appointments, improving the user experience for booking.
Original PR description
The website appointment calendar fills availabilities one month at a time and the update_available_slots route maps the calendar month index to an absolute month from datetime.now(). This only…
The website appointment calendar fills availabilities one month at a time and the update_available_slots route maps the calendar month index to an absolute month from datetime.now(). This only matches the displayed months when the first one is the current month. When the first bookable slot is later, a punctual appointment starting in a future month or any appointment whose "at least X hours before start time" lead time pushes the first slot past the current month, navigating forward requests the wrong month and the reached month renders empty. In update_available_slots, take the lead time into account when computing the reference month so it lands on the first displayed month: the start datetime for a punctual appointment starting in the future, otherwise now plus the minimum schedule hours. The navigated month index is then added to that reference. This extends https://github.com/odoo/enterprise/commit/f0e5b14a823cf97218f4094d287a328e2744fd73 which only handled the future start datetime. Steps to reproduce: 1. Open the Appointments app 2. Open an appointment type, set Schedule to Weekly and Allow Bookings to On specific dates with a range ending a few months out 3. Set the "at least N hours before start time" field to 360 4. Save and click the Preview button in the header 5. Pick a resource or staff member to reach the calendar 6. Click the right arrow to navigate to the next month => the next month shows "Sorry, we have no more slots available for this month" opw-6206293 Forward-Port-Of: odoo/enterprise#120715
This update resolves a technical issue that previously caused errors when users attempted to copy heading links within the knowledge editor. The change removes a dependency on the HistoryPlugin, streamlining the process and ensuring a smoother user experience. This improves the reliability of the knowledge editor for all users.
Original PR description
Prevent traceback when clicking the button to copy a heading link to the clipboard. Technical - Commit https://github.com/odoo/enterprise/commit/70bb74faecadea768bb17a4feb69fa327623ab5d removed the history dependency, although commit() is provided by HistoryPlugin and still requires it. Task-6267431
This change resolves a potential issue during software updates. A previous version of the Point of Sale module caused conflicts with the new stable version, leading to upgrade script errors. Renaming the 'obox_pos' module ensures compatibility and a smooth update process.
Original PR description
A stable module `obox_point_of_sale` was added in saas-19.3 but in master a module `obox_pos` is also present. This will cause some big upgrade script in the FW of `obox_point_of_sale` so renaming the module in master to prevent this error.
This update resolves a problem where test data from one test case was incorrectly carried over to subsequent tests, leading to unreliable results. The fix ensures that the test environment is properly reset after each test, preventing this 'cross-test pollution' and improving the stability of our testing process.
Original PR description
At each test end, the DB is reverted to the Savepoint, but the registry is not reloaded. This causes cross-test pollution This commit fixes this by reloading the registry after each test runbot-error-940278
This update ensures that the employee is automatically selected when creating a new off-cycle payslip. Previously, users had to manually choose the employee, which was a manual and potentially confusing step. This change streamlines the process and improves user efficiency.
Original PR description
Steps to reporoduce: 1) open any employee who has at least one payslip 2) open the employee view and click on payslip smart button 3) List view will open, now click on 'new Off-cycle' button 4) Employee is not there by default. Issue: The employee should be set by default. Solution: Add default_employee_id to the action context so that the employee is set by default when creating a new off-cycle payslip. task-6309649
This update resolves an issue where clickable links within tax return anomaly checks were broken, preventing users from accessing detailed reports and resolving errors. The fix restores the functionality of these cards, allowing users to easily investigate and address tax return discrepancies. This ensures accurate reporting and efficient issue resolution.
Original PR description
Steps to reproduce: - Open tax returns menu items and set opening date - Try to click on an anomaly check -> It should open the corresponding action/view to see the failing records or report to solve the check, but the card is not clickable anymore and the cursor isn't displayed as it should.
This update improves the clarity of payslip reports by only showing bank accounts when there's a positive payment amount. Previously, bank accounts were always displayed, even with zero balances. This change simplifies the report and reduces visual clutter for users.
Original PR description
Now, on payslip's reports, bank accounts are shown at the bottom of the page only if there is a strictly positive amount to pay. task-6311010
This update replaces a problematic function (`cleanTerm`) with a more robust one (`normalize`) in the mail system. Removing the fallback to empty strings prevents hidden errors and ensures data integrity, leading to more reliable email processing.
Original PR description
This commit removes the `cleanTerm` function and replaces its usages with `normalize`. When the value provided to `cleanTerm` is not a string, it falls back to returning an empty string. This is seen as a bad practice, as it could easily hide programming errors. There is no sense to calling `normalize` on something other than a string; if another kind of value ends up in there, it is most likely a mistake. [Task-4818712](https://www.odoo.com/odoo/1519/tasks/4818712) Community: https://github.com/odoo/odoo/pull/262514
This update corrects a display issue where the 'DIMONA Category' column was missing from employee type lists for employee types not associated with a specific country. The fix ensures this column is always visible, regardless of the employee type's country setting, improving data visibility and reporting accuracy.
Original PR description
Steps to reproduce: 1. Install l10n_be_hr_payroll 2. Go to the list view of employee types 3. Show the column DIMONA Category 4. The category is missing for some records (Employee, Student, etc) Cause: The field is invisible if the country of the employee type is not Belgium. But it should still be visible for employee types without a country. Fix: change the invisible condition to allow employee types without country. Task: 6303674
This update ensures that certain Belgian salary rules are only applied to employees with variable salaries. Previously, these rules were incorrectly applied even when no variable salary was configured. The change verifies the contract's 'commission_on_target' field, preventing the rules from being applied in cases where a variable salary isn't present, improving payroll accuracy.
Original PR description
The Belgian salary rules with codes 'COM_LOSS_PH' and 'COM_LOSS_SICK' should only apply to employees who actually receive commissions.
Update the python condition ('condition_python') on both rules to verify that the contract's structure version ('version_id') contains a non-zero value for the 'commission_on_target' field. This ensures these rules are skipped when no variable salary is configured.
Task: 6300080This update corrects a technical error in the Odoo Enterprise payroll module that was causing incorrect cache behavior when rule parameters were missing from the database. The fix ensures that the system correctly identifies missing parameters, preventing errors and improving the stability of payroll calculations. This resolves a potential issue impacting payroll accuracy.
Original PR description
After https://github.com/odoo/enterprise/commit/1ee878fea4e5985852960bb4640a32abfa95ac9e: `_get_cached_parameter_from_code` returns `SENTINEL` when a rule parameter doesn't exist in the DB. `CacheLayer.__getitem__` uses that same `SENTINEL` to detect absent keys. When the stored value IS `SENTINEL`, it is indistinguishable from a missing key; so every subsequent lookup falls through to the parent and raises `KeyError` which `ormcache.lookup()` treats as a miss. applied fix: make _get_cached_parameter_from_code use different object than Sentinel for missing parameters.
This update prevents deleting a batch payment once linked payments have been marked as 'sent' and an XML export file has been generated. This ensures continued compliance with SEPA regulations, which require payments to remain marked as sent. Disallowing deletion maintains the integrity of export files for reporting.
Original PR description
When you create a batch payment, linked payments are marked as sent, and an export file is generated (XML). But if you delete the batch payment, the payments will remain marked as sent, meaning you won't be able to re-generate a new XML file for those payments. As we don't want to unmarked them as sent (we can't for SEPA payments), we decided to disallow the batch payment deletion in those cases. task-6117210 Forward-Port-Of: odoo/enterprise#117748
This update corrects a technical issue in the l10n_ch_reports module that was causing errors during financial report processing. The problem stemmed from a removed subformula not being reset to a default value, leading to incorrect calculations. This fix ensures accurate report generation by setting the subformula value to False.
Original PR description
The subformula was [removed](https://github.com/odoo/enterprise/pull/117601) without resetting its value to False, leaving existing values in the database. This causes errors when processing records that still contain a subformula value. ```.py Invalid subformula in expression "balance" of line "Treasury shares": -sum ``` To prevent these errors, existing subformula values are reset to False opw-6297901 Forward-Port-Of: odoo/enterprise#120663
This update fixes a minor visual issue in the web studio's property tag display within SelectMenus. Previously, tags were limited to 200px, leaving unused space. Now, tags automatically expand to fill the available width, creating a cleaner and more efficient user experience.
Original PR description
Before: Each tag was limited to 200px, leaving available space unused. After: Each tag now expands to 100% of the available width. task-5226503 Forward-Port-Of: odoo/enterprise#120260
This update resolves an issue that caused a traceback when users deleted the last column from a table within the Odoo Report Editor. The fix prevents a technical error by ensuring the editor handles the scenario where a table has no remaining columns gracefully. This improves the overall stability and reliability of the report design process.
Original PR description
Problem: When deleting the last column in a table in studio we get a traceback. Cause: `firstCell` will be null if we delete the last cell in the table. Fix: Added a null check on `firstCell` before calling `setCursorEnd`, so the cursor is only repositioned when the table still has remaining cells. Steps to reproduce: - Edit a report with a table. - Remove all columns. - Traceback will occur when deleting the last one. opw-6263696 Forward-Port-Of: odoo/enterprise#119502
This update fixes a display issue where the AI button was incorrectly shown in the Mass Mailing builder but not the Website Builder. The fix redirects patching to the Website Builder, ensuring the AI button appears only when using the website functionality. This improves the user experience for website visitors.
Original PR description
__Problem__ When opening the Mass Mailing builder after the Website Builder, the AI button is still shown. Conversely, if we open the Website Builder after the Mass Mailing builder, the AI button is never shown. This happens because Owl mounts the Builder component only once as long as we don't refresh the page. Since we patch the generic HTML Builder to put the AI button in the sidebar, the state of the first time it's mounted is preserved. __Fix__ Patch the Website Builder directly instead, as we only want the AI button to be available in the website. Community PR: odoo/odoo#270266 task-6189057 Forward-Port-Of: odoo/enterprise#120688