Daily updates from Odoo
Wednesday, November 6, 2024
6 changes
1 change
Resolved issues and error corrections
Non-image attachments in Discuss now display in a cleaner list layout instead of appearing broken due to an unsuitable grid view. This makes it easier for users to browse and identify attached documents in conversations.
Original PR description
The grid layout in attachment list makes the non attachment list view look broken. This commit removes the grid from this view. Steps to reproduce: - open a discuss channel - add some non image attachments - go to the attachments list Backport of https://github.com/odoo/odoo/pull/186033
1 change
Resolved issues and error corrections
This fix corrects a report generation method name for GSTR-1 and updates the GSTR-2B status spelling from "recived" to "received". It helps avoid confusion and potential errors when handling Indian GST return periods.
Original PR description
This **PR**, rectifies method name for GSTR-1 report generation and corrects GSTR-2B status spelling from 'recived' to 'received'. **task**-4306959 **Upgrade PR** - https://github.com/odoo/upgrade/pull/6717
4 changes
Resolved issues and error corrections
This update resolves an issue where Helpdesk teams weren't displaying all relevant non-billable projects in their dropdown menus. The fix ensures that projects are correctly identified regardless of billing settings, and also corrects a bug where disabling Time Billing kept projects in an unexpected state. This improves team efficiency and data accuracy.
Original PR description
### Current behavior before PR: When creating a Helpdesk team and the Timesheets option enabled and Time Billing disabled you will not get all non-billed projects in the dropdown menu. This is…
### Current behavior before PR: When creating a Helpdesk team and the Timesheets option enabled and Time Billing disabled you will not get all non-billed projects in the dropdown menu. This is happening because the domain for project_id is checking the company_id to be the same as the company_id of the team. https://github.com/odoo/enterprise/blob/18.0/helpdesk_sale_timesheet/models/helpdesk_team.py#L10 Though since this commit https://github.com/odoo-dev/odoo/commit/16a07ed1bfd33a193b363f3e87aab3f9bd6f8bd0 company_id is not required for projects. Since the domain of the project_id field was introduced here https://github.com/odoo/enterprise/pull/4956/commits/c82b1b019cebd1f78749b9563e717fae88d7fae5 and the reason why we check the company_id is not the same anymore since the commit I mentioned above we should not use the same domain. Also in this PR we are solving another issue which is where you enable both Timesheets and Time Billing options and choose a project that has both options enabled too then you disable the Time Billing option for the team the project that we chose before will be kept and have both options enabled and you can save it. ### Desired behavior after PR is merged: We are now checking for the project of the team if the company_id is False or equal to the team's company_id. Also when disbaling the Time Billing option we set the project_id to False. opw-4275647 opw-4148207
This update fixes an issue where duplicated shifts didn't correctly calculate allocated hours for different employees. Previously, duplicated shifts would incorrectly show 8 hours instead of the expected hours based on the employee's working schedule. This ensures accurate shift planning and time tracking.
Original PR description
Steps to reproduce: ------------------- 1. Install Planning app 2. Have an employee A with 40h/week working schedule and an employee B with 35h/week working schedule 3. Create a shift and assign it to employee A, the default allocated hours should be 8h 4. From the Gantt view, duplicate this shift and assign it to employee B (use drag and drop) 5. Problem: The allocated hours of the duplicated shift are not recomputed, they are equal to 8h instead of 7h Fix: ------------------- When duplicating a shift and assigning it to another resource, the copy() method is called with the resource_id of the target resource (an employee in this case). But _compute_allocated_hours() is not called so we have to call it explicitly in this case. version-17.0 task-3978590
This update resolves a bug where the 'release_to_pay' field in invoices was incorrectly reverting to 'Yes' after saving, even when set to 'No'. This issue prevented accurate payment processing. The fix ensures the field's value is correctly saved based on user selections.
Original PR description
**Steps to reproduce:** - Install account_3way_match - Go to "Invoicing / Vendors / Bills" - Create a bill - (Edit the view in order to display "release_to_pay" field) - (Make sure that "Force Status" (force_release_to_pay) is always checked) - Set "Should Be Paid" (release_to_pay_manual) to "Yes" => "release_to_pay" becomes "Yes" - Save the bill => "release_to_pay" stays "Yes" - Change "Should Be Paid" to "No" => "release_to_pay" becomes "No" - Save the bill => "release_to_pay" reverts to "Yes" **Issue:** Upon save, "release_to_pay" reverts to "Yes", even if it has been correctly computed to "No" before saving. opw-4181752 Forward-Port-Of: odoo/enterprise#72190
This update resolves an issue where the 'Requests to switch' filter incorrectly identified future shifts as past, due to timezone discrepancies. The fix ensures shifts are accurately displayed based on their actual time, regardless of the user's location, improving scheduling accuracy.
Original PR description
The 'Requests to switch' filter is supposed to show slots that are unwanted and that are not in the past. Prior to this commit, some shifts that were in the future were not shown by the filter. That was because the planning.slot field end_datetime was encoded in UTC while the datetime.datetime.now() function in the filter's domain was returning the datetime in the client's timezone. Shifts in the time difference between the user's timezone and UTC would be mistakenly marked as "past shifts" while they might still be in the future. We fix this by using the 'to_utc()' function which should make the filter domain's comparisson between 2 UTC datetimes. Fix done in 17.0 task-4286161