odoo/odoo#148689
Created by fw-bot
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/template: Contact runbot team on discord for help.
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
- ci/documentation: (runtime 132s)
- label
- odoo-dev:saas-16.3-16.0-fix-microsoft-calendar-organizer-email-vl-7-fw
- head
- 28cfef462876ddd212ad0e45cfdafe42b3108798
- merged
- 2 years ago by Misc, Arnaud Joset (arj)
| odoo/odoo | |
|---|---|
| 16.0 | #147069 |
| saas-16.1 | #148653 |
| saas-16.2 | #148666 |
| saas-16.3 | #148689 |
| saas-16.4 | #148702 |
| 17.0 | #148715 |
| saas-17.1 | #149460 |
| 18.0 | |
| saas-18.2 | |
| saas-18.3 | |
| saas-18.4 | |
| 19.0 | |
| saas-19.1 | |
| saas-19.2 | |
| saas-19.3 | |
| master | #148733 |
[FW][FIX] microsoft_calendar: Make searching organizer by their email address case-insensitive
Description of the issue/feature this PR addresses:
When a calendar event gets synchronized from Outlook calendar to Odoo in which the organizer's email address' capitalization doesn't match between Outlook and Odoo, the event is created in Odoo without an organizer. (i.e. user_id is False)
Current behavior before PR:
If the organizer's email address is Firstname.Lastname@example.com in Outlook and firstname.lastname@example.com in Odoo, the event is created in Odoo without an organizer.
Desired behavior after PR is merged:
Odoo is able to find the correct organizer user ID even though the capitalization of the email address wouldn't match.
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: #147069