Thursday, April 30, 2026
4 changes · saas-18.2
Resolved issues and error corrections
Customer searches by email now check the correct email field instead of the phone field. This helps customer records be found reliably when an email address is used, reducing missed matches in accounting workflows.
Original PR description
The email-based lookup was mistakenly checking the phone field (`phone = email`) instead of the email field. Because of this, customers could not be correctly found using their email address. This change fixes the domain to properly match on the email field. Forward-Port-Of: odoo/odoo#260567
Adding attendees to calendar events that already happened will no longer send invitation notifications. This prevents confusing or unnecessary emails for outdated meetings and keeps calendar communication relevant.
Original PR description
Backport of fix in 19.0 (https://github.com/odoo/odoo/pull/259844) Prevents invitations to be triggered when adding new attendees to an event in the past. OPW-6125052 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#261599 Forward-Port-Of: odoo/odoo#260050
Event registration pages no longer show the original ticket price as struck through when a fixed-price pricelist rule is used. This prevents fixed event prices from being mistaken for discounts and aligns event ticket pricing with the online shop experience.
Original PR description
Event tickets show a struck-through original price even when a "Fixed Price" pricelist rule is applied, making it incorrectly appear as a discount. This is inconsistent with eCommerce shop behavior.…
Event tickets show a struck-through original price even when a "Fixed Price" pricelist rule is applied, making it incorrectly appear as a discount. This is inconsistent with eCommerce shop behavior. ### Steps to reproduce 1. Create an event with a paid ticket (e.g., 100 EUR). 2. Create a pricelist with a "Fixed Price" rule for that ticket (e.g., 80 EUR). 3. Open the event registration page. 4. The 100 EUR appears struck-through next to 80 EUR. ### Cause Odoo's website only shows a struck-through original price for discount rules, not fixed price rules. By design, a fixed price replaces the original rather than reducing it. However, the event registration page used a simplified check: it compared the final price to the original and assumed any difference was a discount. This ignored the rule type, incorrectly flagging fixed price rules as discounts. ### Fix Rationale A new helper method on the event ticket model now queries the applied pricelist rule to determine if it qualifies as a discount. opw-5993477 Forward-Port-Of: odoo/odoo#252257
This update fixes an issue where report data, particularly those using the 'From the very start' period, was not sorted correctly. The change ensures that string-type external values are properly ordered by date when using the 'most_recent' formula, improving report accuracy and reliability.
Original PR description
Ensure string-type external values are correctly sorted by date when using the "most_recent" formula. This resolves an issue where values appeared unordered, especially for expressions using the "From the very start" period. task-5951888 Forward-Port-Of: odoo/enterprise#114666 Forward-Port-Of: odoo/enterprise#113837