Thursday, February 16, 2023
4 changes · master
Resolved issues and error corrections
User logins that are typically email addresses are now checked without regard to uppercase or lowercase letters. This prevents duplicate accounts using the same email in different casing, avoiding confusion with notification preferences and profile settings.
Original PR description
login field is usually used for email. The email addresses are case insensitive, so xxx@example.com and XXX@example.com should be considered as the same. Previous implimentation was case sensitive, which may lead to a confusion on the following scenario: * create two users with the same email typed in a different cases * merge related partners * ping the user in a chatter * RESULT: notification settings (email/inbox) are used from the first user, which might be different from what user sees in their Profile settings opw-2908939
Point of Sale now records sales of product kits using the kit's own expense account instead of the accounts from its individual components. This keeps POS accounting consistent with Sales and helps ensure costs are reported under the right product category.
Original PR description
If kit's category has different expense account than its components, then we should use kit's account. Such logic is already done in the Sales app, however before this commit the component's settings were used on selling via POS. opw-2930819 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 fix allows employees to create timesheets for projects whose analytic account is not tied to a specific company. It prevents unnecessary timesheet creation failures in shared or company-neutral project setups.
Original PR description
This commit's purpose is to allow the creation of timesheet even if the analytic account of the project has no company_id 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 fixes an issue where user avatar fields in kanban views could use the wrong display component. The change helps ensure assigned users or collaborators are shown correctly, improving clarity in records that rely on avatar-based user lists.
Original PR description
Before this commit, since the commit [1] changing the field registry, the component used for the `kanban.many2many_avatar_user` widget is not right one. This commit fixes the issue by setting the right component for the widget. [1] 9f4622492c5cd84847368d32bf02b0b538a6dd69