Thursday, April 9, 2026
12 changes · master
Enhancements to existing features
This update adds a warning message in the gift card wizard to prevent users from creating gift cards with expiration dates in the past. This ensures data accuracy and prevents potential issues with gift card redemption. It's a simple improvement to the gift card generation process.
Original PR description
Display a warning in the gift card wizard when the selected valid_until date is in the past, prompting the user to select a valid date. task-5075177
This commit reverts recent changes related to M3, restoring the previous template structure with necessary adaptations. This ensures consistent formatting and functionality across key modules, improving the user experience and stability. The change addresses a technical update to align with a previous style.
Original PR description
This commit reverts the changes made for M3 to the arch, and bring back the previous template with some adaptation when needed. task-6054024 Co-authored-by: Romeo Fragomeli <rfr@odoo.com> Co-authored-by: Adrien Dieudonné <adr@odoo.com>
This update adjusts the form view for combined work entry types following a recent merge of work entry and time off types. The changes ensure both functionalities work seamlessly after the integration, streamlining the process for managing employee work entries.
Original PR description
After the merge of work entry type and time off type in https://www.odoo.com/odoo/project/1251/tasks/5407736, the form view needed some fixes and tweaks. Fields were moved around the sections of the form view, and some redundant fields were removed/altered to have both old functionalities working. task-5942695
This update clarifies the input fields used when calculating termination fees in payslips. The original 'days,' 'weeks,' and 'months' fields have been renamed to 'Notice Duration: Number of days/months/years' for better user understanding. This change improves the accuracy and transparency of the termination fee calculation process.
Original PR description
[IMP] l10n_be: renaming salary rules in termination fees When termination fee is selected in payslip creation, there were property inputs named as days, weeks, months I renamed them to "Notice Duration: Number of days/months/years" task - 6106963
Resolved issues and error corrections
This update adjusts the VAT number used in the 'L10nThaiTaxReportTest' test case to align with recent changes in how companies and individuals are created within Odoo. This ensures accurate reporting and tax calculations for Thai businesses.
Original PR description
in this commit:- - We're changing partner's vat in 'L10nThaiTaxReportTest' and adopting new vat as per new way of creating company and individual. as `branch name` is depend upon 'is_company'. - see https://github.com/odoo/odoo/commit/f6e431c813787958897526a4d6570124048b428a task-6002111 Forward-Port-Of: odoo/enterprise#113236 Forward-Port-Of: odoo/enterprise#112434
Features or functions removed from Odoo
This update removes an unnecessary step when sharing helpdesk tickets through the forum. Previously, sharing a ticket automatically created a new message. This change streamlines the process and improves the user experience. It's a minor update that enhances the forum's functionality.
Original PR description
Purpose ======= Remove the `message_post` on the forum post when sharing a ticket in forum, because it no longer inherits from `mail.thread`. Task-3586524
This update fixes an issue where chart links weren't directing users to the correct view type (e.g., a list view for a list datasource). Previously, links defaulted to the standard action view, leading to an inconsistent user experience. This change ensures chart links now accurately navigate to the appropriate view for each datasource type.
Original PR description
Currently, if the user clicks on a datasource link (inside a chart) they will be directed to the default view of the action realted to the datasource model but it will not go to the corresponding type of view (e.g. a list datasource should direct to a list view). Task-5957004 Forward-Port-Of: odoo/enterprise#113211 Forward-Port-Of: odoo/enterprise#108158
This update resolves an issue where manual digitization of vendor invoices was blocked if the bill date wasn't initially set. The change allows users to trigger digitization without a bill date, while still ensuring data consistency through a validation step afterward. This improves the flexibility of the invoice digitization process.
Original PR description
### Issue: When setting Vendor Bills to Digitize on demand, it is no longer possible in 19.0 to trigger digitization manually if the Bill Date is not set A missing required fields error is raised ###…
### Issue: When setting Vendor Bills to Digitize on demand, it is no longer possible in 19.0 to trigger digitization manually if the Bill Date is not set A missing required fields error is raised ### Cause: This PR: https://github.com/odoo/odoo/pull/238911 introduced a required field to prevent an error modal from appearing While this works as intended, it also blocks the `Digitize Document` action, which is supposed to populate the Bill Date automatically ### Fix: A condition similar to the one used for the Digitize Document button is applied to allow triggering digitization without a Bill Date The validation modal is still enforced afterward to ensure data consistency in case of manual edits ### Steps to reproduce: - Install `account` - In Settings, set `Document Digitization` for `Vendor Bills` to `Digitize on demand only` - Create and print an invoice (any data) or use an existing one - Import it into Vendor Bills - Click Digitize Document ### Before the fix: A missing required fields notification is raised, preventing digitization opw-5886012 Forward-Port-Of: odoo/enterprise#112585
This update fixes a minor issue in the knowledge history tour by adding a new step, ensuring a more complete and accurate user experience. This enhancement improves the onboarding process for new users and provides a clearer demonstration of the knowledge base features.
Original PR description
Fix tour by adding a new step.
This update corrects a stability issue within the Odoo Enterprise expense reporting module. By switching to a 'TransientModel' for the wizard, the system is now more reliable and efficient. This change ensures smoother operation of the expense tracking process.
Original PR description
`HrExpenseStripeTestPurchaseWizard` is currently using a normal `Model`, but it's a wizard, so use a `TransientModel`. Forward-Port-Of: odoo/enterprise#113313
This update ensures the demo data for the Turkish payroll module correctly references the state IDs. Previously, demo data used outdated state information, leading to potential errors. This change improves the accuracy and reliability of the demo environment for Turkish payroll setup.
Original PR description
Previously, all the turkish states were defined in the base module, but were moved to l10n_tr. This comit makes sure that demo data uses the correct state ids task-5945331
A technical issue preventing users from accessing the timesheet assistant was fixed. This involved correcting a duplicate key error in the configuration file, ensuring a smoother user experience when taking suggestions for timesheets. The change improves stability and usability of the timesheet feature.
Original PR description
In PR: https://github.com/odoo/enterprise/pull/108360/changes `aw_local_config.js` was replaced by `frequency_viewer_local_config.js` but in the Forward from saas-19.1 to saas-19.2, both files were maintained https://github.com/odoo/enterprise/commit/3ced9cf68affd973c570e92627361cd0db8eb518 Forward-Port-Of: odoo/enterprise#112639