Thursday, August 5, 2021
5 changes · master
Resolved issues and error corrections
The project overview now checks directly whether a project has timesheets instead of calculating total timesheet time first. This reduces unnecessary processing and should make the project kanban view load more efficiently when timesheets are present.
Original PR description
Before this commit, we use the `total_timesheet_time` field in the kanban view of `project.project` to know if there are some timesheets into each project. The problem is this field is computed and its compute method take more execution time than just use `timesheet_ids` field to allow if a project has at least one timesheet. This commit replaces the using of `total_timesheet_time` field by the `timesheet_ids` field in project kanban view to check if the project has at least one timesheet. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The mail menu unread counter now excludes channels that are not pinned, preventing hidden or inactive conversations from inflating the displayed unread count. This helps users see a more accurate notification number for the conversations they actively keep in their menu.
Original PR description
Follow up of a795a2f7d8fd57120db5cafdc9f1929e118b0626
Adyen payment notifications will now always receive the expected confirmation response, even if Odoo encounters a validation issue while processing them. This avoids exposing internal error details in Adyen's backend and keeps payment notification handling cleaner and more consistent.
Original PR description
Before this commit, when the webhook was processing a notification, if there was a validation error, the webhook was sending the whole traceback to Adyen. Since this was still a response code 200, this didn't cause any problem, but we could see the response received in the Adyen backend. So we will now catch any validation error and send `'[accepted]'` in the response.
This fix ensures that when an Italian SdI Coop electronic invoice is sent successfully, the system reports the success correctly. This helps prevent follow-up processes or user feedback from treating a successful send as uncertain or failed.
Original PR description
…d return {'success': True}
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-prPoint of Sale users now see an error message when they select a loyalty reward for a free product that is not available in the POS. This prevents silent failures and helps staff understand why the reward cannot be applied.
Original PR description
This PR addresses multiple small changes for the POS according the task 2492631 which are: - Added an `ErrorPopup` when selecting a free product which is not loaded in the POS as a reward. - ~~Properly load the rewards and rules of the corresponding (only one) Loyalty Programs~~ (fixed in 0fbdbd082209f8f408c1a88f969a4fab26fd1589) Related community PR: https://github.com/odoo/odoo/pull/72793