Daily updates from Odoo
Sunday, June 7, 2026
5 changes
2 changes
Resolved issues and error corrections
This update resolves an issue where non-internal users accessing field service reports through the portal couldn't view attached photos. The fix ensures that all users, including customers, can now see the images linked within the reports, improving the customer experience and report clarity. This was achieved by granting appropriate access tokens.
Original PR description
Photos were not accessible in the portal field service report for non-internal users. **Steps to reproduce** - Create a planning slot, set a portal user as the customer and mark the slot as "Completed". Add an image in the chatter. - Logged in with the customer's portal user account, access the field service report in the portal. The "Photos" section displays the name of the picture, but it is not possible to view it. <img width="888" height="320" alt="image" src="https://github.com/user-attachments/assets/523d1d1a-7c9c-4c9a-85f5-acd4df86d7ff" /> **Change** Similar to what is done in `project/controllers/portal.py` to give access to attachments to non-internal users from the portal, generate the necessary access tokens. opw-6236038
This update optimizes how global filters are applied in the spreadsheet module, reducing unnecessary server requests and reloads. By batching filter updates, the system now handles multiple filter changes more efficiently, leading to faster dashboard responsiveness and reduced server load. This improves the overall user experience, especially when working with complex data sets.
Original PR description
## Description of the issue/feature this PR addresses: Current behavior before PR: - Applying multiple global filters triggered one command per filter. - Each command reloaded all data sources (pivot/chart/list). - This caused redundant RPC calls: (no of filter change * no of data sources). - With many filters and data sources, server load increased heavily and could lead to slowdowns or 502 errors. Desired behavior after PR is merged: - Use `SET_MANY_GLOBAL_FILTER_VALUE` to update filters in batch. - Data sources are reloaded only once per batch update. - RPC calls and reload now scale with number of data sources only. Impact: - Significantly reduces server calls when applying multiple filters. - Improves dashboard responsiveness and avoids server overload. Task: [6216133](https://www.odoo.com/odoo/project/2328/tasks/6216133) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#264314
2 changes
Resolved issues and error corrections
This update prevents users with limited access from modifying timesheet entries automatically generated for public holidays. Previously, these entries were editable, leading to potential inaccuracies in reporting and payroll. This change ensures data consistency and aligns with standard time-off entry behavior.
Original PR description
Timesheet entries generated from public holidays are currently editable by users with minimal rights. Although these entries appear greyed out, they can still be modified, which can lead to inconsistencies in reporting and payroll calculations. This behavior is inconsistent with other time-off–related entries, which are non-editable by default. Hence, this commit makes global time off timesheet entries non-editable in all views, except the grid, which instead displays a user error if they try to edit the timesheet amount. Backport of odoo/odoo#248282 Forward-Port-Of: odoo/odoo#268314
This update optimizes how filters are applied in the spreadsheet module, reducing the number of server requests and improving dashboard responsiveness. By batching filter updates, the system avoids redundant data reloads, leading to a smoother and faster user experience, especially when applying multiple filters.
Original PR description
## Description of the issue/feature this PR addresses: Current behavior before PR: - Applying multiple global filters triggered one command per filter. - Each command reloaded all data sources (pivot/chart/list). - This caused redundant RPC calls: (no of filter change * no of data sources). - With many filters and data sources, server load increased heavily and could lead to slowdowns or 502 errors. Desired behavior after PR is merged: - Use `SET_MANY_GLOBAL_FILTER_VALUE` to update filters in batch. - Data sources are reloaded only once per batch update. - RPC calls and reload now scale with number of data sources only. Impact: - Significantly reduces server calls when applying multiple filters. - Improves dashboard responsiveness and avoids server overload. Task: [6216133](https://www.odoo.com/odoo/project/2328/tasks/6216133) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#264314
1 change
Resolved issues and error corrections
This update resolves an issue where shift allocations incorrectly showed 0% when created on weekends, preventing accurate hour calculations. Additionally, a test was modified to skip running when demo data is present, ensuring consistent test results. These changes improve the reliability of shift planning and testing processes.
Original PR description
## [FIX] planning_field_service: avoid division by 0 Before this commit, when the shift is created during the weekend, the allocated_percentage will be 0 percent because the resource assigned is not…
## [FIX] planning_field_service: avoid division by 0 Before this commit, when the shift is created during the weekend, the allocated_percentage will be 0 percent because the resource assigned is not supposed to work at that day and so a division by zero occured in the onchange of break_time field in planning.slot model. This commit checks if allocated_percentage is not equal to 0 before computing the new allocated hours when the user alters break_time field on a planning.slot. ## [FIX] planning_field_service: don't start test with onboarding tour with demo Before this commit, the planning_field_service_tour tour does not work when there is demo data because the tour will select the first slot in the gantt view which will be an open shift instead of a shift assigned to the current user because of that, the sign in button is not displayed as expected. This commit makes sure the test running the planning_field_service_tour tour is skipped when demo data are installed. runbot-error-242483 Forward-Port-Of: odoo/enterprise#119032