Monday, July 14, 2025
7 changes · 17.0
Resolved issues and error corrections
This change adjusts when a profitability test runs so it has the required accounting setup available. It helps avoid false test failures in environments without demo data, improving confidence in release checks without changing customer-facing features.
Original PR description
One of the tests failed without demo data due to a lacking stock accounting account. Since the test requires the Chart of Accounts, it was moved to post-install. runbot error: [163084](https://runbot.odoo.com/odoo/error/163084) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Recruitment stages no longer allow quick creation of email templates that are missing required setup information. This prevents errors when applicants are moved into a stage using one of those templates, making the hiring workflow more reliable.
Original PR description
An error occurs when a user quickly creates a template for a stage, bypassing the validation of the `Applies to` field. As a result, an error is triggered when the user selects a stage that uses that template. **Steps to reproduce:** * Install `hr_recruitment` * hr_recruitment>Configuration>Stages>stage named `New`>Quick Create a mail template with random name and save. * Applications>All Applications>New application>Set stage to `New` `KeyError:False` **Solution:** * Disable quick create as to prevent creating mail templates with empty model ids. **Sentry-6675399135** --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When users move from one record to another using the pager, a soft reload now refreshes the record they are currently viewing instead of reverting to the first record opened. This prevents confusion and helps ensure actions from form buttons update the right business data without forcing a full page reload.
Original PR description
Backport of https://github.com/odoo/odoo/pull/195907 opw-4847873
Users can now update progress bar values reliably in Firefox. This fixes a browser-specific issue where changes entered in progress bar fields were not saved, improving consistency across supported browsers.
Original PR description
Before this commit, the input of the progressbar field couldn't be updated on firefox. It works on the other browsers by chance. In the list renderer, we call `preventDefault` on enter keydown. The event is first catch by the list renderer. This call is enough to prevent "change" event to trigger but on chromium browsers it is actually triggered (but should not). The progressbar field catches it and saves the new value. On firefox, the "change" event is never triggered. The commit fixes the input by using the input field hook to make it behave correctly. task-4881210
A small wording typo in the portal sharing flow was fixed, with minor cleanup to make the related code clearer. This reduces confusion in the user-facing portal sharing experience without changing functionality.
Original PR description
fix a small typo and and refactor for clarity opw-4938011 Forward-Port-Of: odoo/odoo#218570
This fix ensures Nilvera documents use the appropriate UBL TR format instead of Peppol-specific handling. It matters because Nilvera is not a Peppol format and should not rely on Peppol fields, reducing the risk of incorrect electronic invoice data.
Original PR description
It's not a format that is on peppol and does not use the fields from peppol. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects an issue in the accounting reports tax report area. It helps ensure tax report results behave as expected, reducing the risk of confusing or incorrect reporting output for users.
Original PR description
Test runbot of the backport of https://github.com/odoo/enterprise/commit/c93388741182f1873054557a6e7767186674fafa#diff-2ef638bc57a617093728802f175080339d8c7843bbad7e8b72ef57167ced85a7 opw-4911229