Tuesday, April 14, 2026
8 changes · 17.0
Resolved issues and error corrections
This update corrects a recent issue with accounting dates used in payroll journal entries. It reverts a previous change that was causing inaccuracies in financial reporting. This ensures payroll accounting aligns correctly with company financial records.
Original PR description
This reverts commit 01717c6fdb6bbbc3149048f6284807c7fc36f540. Task: 6116315
This update resolves an issue preventing correct invoice report naming in the Mexican tax module (l10n_mx_edi). It aligns with a recent community update, ensuring compatibility and preventing errors during invoice sending. This improves the reliability of invoice processing.
Original PR description
Update _get_invoice_report_filename override to accept the optional report parameter and forward it to super(). This is a compatibility fix linked to the community PR, which extends the base helper to support dynamic report naming. Without this update, the enterprise override still uses the old signature and causes errors in invoice send flows. This change ensures compatibility with the updated helper in account and prevents errors in invoice send flows when a report is provided. Related Community PR: https://github.com/odoo/odoo/pull/256204 Related Ticket: opw-6058716
This change removes a confusing tooltip from the calendar popover for boolean fields. The tooltip was displaying unnecessary HTML content, creating a poor user experience. This improvement simplifies the calendar interface and enhances usability.
Original PR description
Before this commit, the tooltip of a boolean field in calendar popover shows html content when the user hovers the boolean field. This commit removes the tooltip of boolean field in calendar popover since the information inside that tooltip is not really useful for the user. Issue found during the development of task-5994205
This update resolves an issue where printing surveys didn't display participant answers, leading to incomplete reports. The change ensures all survey responses are always included when printing, providing more accurate and reliable data. This improves the quality and consistency of survey results.
Original PR description
Previously, printing surveys of type scoring_without_answers omitted participants' answers, resulting in incomplete and inconsistent reports. This commit ensures answers are always included, regardless of survey type. Task-5407701 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#258616
This update resolves an issue where a previous manager would continue to receive department messages after a new manager was assigned. Now, when a manager is reassigned, they are automatically unsubscribed from all department communications, ensuring a cleaner and more accurate notification system. This improves the user experience for both managers and department members.
Original PR description
…ager is assigned 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
This update corrects a technical issue where an old manager would continue to receive department messages after a new manager was assigned. The change ensures that users are only notified about relevant department communications, improving email efficiency and reducing potential confusion. This is a minor fix impacting the HR module.
Original PR description
…ager is assigned 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
This update resolves an issue where a previous manager remained listed as a follower after a new manager was assigned. The change ensures that the old manager is automatically unsubscribed from the department, maintaining accurate follower lists and streamlining organizational updates. This improves data accuracy and reduces potential confusion.
Original PR description
Description of the issue/feature this PR addresses: old manager is still in followers after changing Current behavior before PR: old manager is still in followers after changing Desired behavior after PR is merged: old manager gets unsubscribed to the department --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update ensures that invoices sent via email now use the custom 'Printed Report Name' configured for reports, rather than a default naming pattern. The change corrects a previous issue where invoice emails incorrectly generated attachments with generic names, leading to potential confusion and misidentification of documents. This improves the clarity and professionalism of invoice communications.
Original PR description
When sending an invoice by email template, the generated PDF attachment does not use the configured Printed Report Name. Instead, it falls back to a default naming pattern (e.g. report action name +…
When sending an invoice by email template, the generated PDF attachment does not use the configured Printed Report Name. Instead, it falls back to a default naming pattern (e.g. report action name + invoice number). This is due to a difference in flow: sales use the standard mail.compose.message wizard, which correctly applies each report’s print_report_name, while invoices use the dedicated account.move.send wizard. In the invoice flow, _get_placeholder_mail_template_dynamic_attachments_data uses the invoice report context instead of the actual dynamic report. To fix this, the send flow is updated so _get_placeholder_mail_template_dynamic_attachments_data computes the filename from extra_mail_template. Additionally, _get_invoice_report_filename needs to be extended in 17.0 to optionally accept a report and use its print_report_name like in the newer versions while preserving fallback behavior. The safe_eval is taken from code used in the future version's code, and is needed as the field accepts python expressions. This naming issue occurs from 17.0 to current master, and the fix will ensure extra dynamic reports follow their configured printed name. Steps to reproduce: Go to Settings > Technical > Reporting > Reports and duplicate the standard Invoice report. In the duplicated report, set a custom value in Printed Report Name (e.g. 'CUSTOM_NAME_TEST'). Go to Settings > Technical > Email > Templates and open “Invoice: Send my email”. Add the duplicated report under Dynamic Reports. Create a customer invoice and confirm it. Click Send (or Send & Print) to open the email preview. Related Ticket: opw-6058716