Wednesday, March 20, 2024
10 changes · saas-17.1
Resolved issues and error corrections
The Planning profile button now appears correctly when both the logged-in user and the target employee belong to multiple companies. This fixes a visibility issue so users can reliably access employee profile details in multi-company setups.
Original PR description
Currently, when the user and the target both are in multiple companies, the profile button cannot be displayed correctly. Since the employee_id uses `('company_id', '=', self.env.company.id)` rather than `in`.
In community branch we fixed it by checking employee_ids directly and if it is found, the profile button will be displayed correctly.
In order to accommodate that change, we needed to filter out employee_ids and add employee_id in fields for patchAvatarCardResourcePopover, as resource.resource has no field employee_ids.The salary package wishlist now groups available cars by category, matching the company car benefit experience. This makes it easier for employees to browse and compare vehicle options consistently.
Original PR description
Since the wishlist benefit displays cars, they should be grouped by category as for the Company car benefit.
The Studio app creation screen has been adjusted so the final “Create your App” button remains clearly visible in Chrome at normal zoom. This removes the need for users to zoom out and helps them complete new app creation without confusion.
Original PR description
Steps to Reproduce : - Toggle Studio from Odoo Dashboard - Click on create new app button --> Enter App name and Respective model - The `Create your App` button in Chrome will ultimately not be clearly visible at 100% zoom; the user must currently zoom out to see the button. video link: [Video](https://drive.google.com/file/d/1ug8VFpC10l4o_HFRQOnvwbUDO9yg_rzq/view) Observed behavior: - `Create your App` button is not visible. Expected behavior: - `Create your App` button should be visible clearly. Task-3794467
This update resolves an issue where users could interact with the 'load more' button in the Kanban view when the system was running on sample data. This change ensures that the Kanban view functions correctly, regardless of whether it's using live data or a sample dataset, improving user experience.
Original PR description
This commit fixes an issue where one could interract with the load more button of the kanban view even in sample data mode. task-3754233
This update resolves an issue where the profile button wasn't appearing correctly when users and targets were associated with multiple companies. The fix now accurately checks for employee IDs across all companies, ensuring the profile button is displayed as expected for users with complex company relationships.
Original PR description
Currently, when the user and the target both are in multiple companies, the profile button cannot be displayed correctly. Since the employee_id uses `('company_id', '=', self.env.company.id)` rather than `in`.
This commit fixes the issue by checking employee_ids directly and if it is found, the profile button will be displayed correctly.
We don't care about which employee_id is used if there are multiple, since the user are in multiple companies as well. If looking for a specific profile, the employee can be found in the HR application.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#157741The project task progress bar was incorrectly displaying a value of '1' instead of '100' when timesheets were logged. This update corrects a calculation error that was introduced recently, ensuring the progress bar accurately reflects the percentage of time logged on tasks. This improves the visibility and accuracy of task progress for users.
Original PR description
### Steps to reproduce: - Install **Field service** app. - Go to Field Service app and create a new task, with Allocated Time of 5 hours. - In the new ticket, Log 5 hours in the **TimeSheets** tab. - Go to the tasks list. - Notice how the progress bar of the new task shows **1** _instead_ of **100** although 5 out of 5 hours have been logged. ### Investigation: - 8389722b1abdef029799c3c082a44e30dafb24b1 introduced the new **ProjectTaskProgressBarField** component. - 4a93d9aee957dd3feb3db0cb69eb3b8f0f4a4683 introduced a change to calculate the `task.progress` as a _fraction_ instead of a _percentage_ https://github.com/odoo/odoo/blob/7280dd53bc14f7c398c63a1f719987bcab7c257a/addons/hr_timesheet/models/project_task.py#L102 - But the **ProjectTaskProgressBarField** wasn't adapted to that change working with percentage values. opw-3790397
This update corrects a formatting issue in the Czech localization for Odoo. It ensures that the Company ID (IČO) is displayed before the VAT ID (DIČ), aligning with Czech reporting standards. The change also clarifies the label for the Company ID to 'Company ID' for better readability.
Original PR description
In Czech republic, the standard is to first render Company ID (IČO), and then to render VAT ID (DIČ). - Changing the position to before (not after), so company ID renders before VAT ID. - Changed label from "ID" to "Company ID" (so it is obvious in what ID it is). Original fixes by @cunivca: odoo/odoo#149339, odoo/odoo#149340, merged into one. Related: https://github.com/odoo/odoo/commit/d0704a19de31e0251d343081ae6b3da9991a248e Forward-Port-Of: odoo/odoo#157993
This update corrects a visual issue where the 'billable' message within the project timesheet was incorrectly positioned. The fix involved refining the system's targeting of the message element, ensuring it appears in the correct location for users. This improves the clarity and usability of the timesheet feature.
Original PR description
Versions: --------- - 17.0 Issue: ------ Message for flag timesheet from project as billable/non-billable is misplaced. Cause: ------ Xpath given for Message placed in sale_timsheet is not very specific. Solution: --------- Give accurate xpath for message div. task-3630449 Forward-Port-Of: odoo/odoo#148880
This update resolves a sporadic failure in a key WebSocket test, ensuring more reliable test results. The fix addresses a timing issue where the test was prematurely evaluating the connection before it was fully established. This improves the overall stability of the Odoo platform.
Original PR description
Before this commit, the `test_websocket_instances_weak_set` was sometimes failing. Indeed, this test doesn't wait for the connection to be fully established before making its assertions. This commit fixes this issue. fixes runbot-55037,55035 Forward-Port-Of: odoo/odoo#157510 Forward-Port-Of: odoo/odoo#157433
This update resolves an issue where a manufacturing smart button was incorrectly displayed during resupply picking for subcontracting orders. The change ensures that this button is hidden, aligning with the intended workflow and preventing potential user confusion. This improves the user experience and data accuracy for subcontracting processes.
Original PR description
Create a [TEST] product: - Routes: - Replenish on Order (MTO) - Buy Assign to [TEST] the following Bill of Material: - BoM Type: Subcontracting - Subcontractors: [Partner] - Components: - [component 1] - [component 2] Components are set up as follows: - Routes: - Buy - Resupply Subcontractor on Order Now create a PO: - Partner: [Partner] - Product: [TEST] Confirm the PO Go to the created resupply picking Issue: there is a smart button for manufacturing The MO should not be visible and the smart button should not be there. opw-3801113