Thursday, September 9, 2021
5 changes · master
Resolved issues and error corrections
This fixes an issue where attendee answers to registration questions were not being stored when completing an event signup. Businesses can now reliably collect the information they request from every event registrant.
Original PR description
When questions are displayed in the form for a registration, the answers were not save. Now, the answers are saved for all the registrations 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 update fixes issues in the accrued sales and purchase order wizard that could reset user-entered values and prevent validation. It also improves the resulting accrual entries by making them clearer and less cluttered for accounting review.
Original PR description
* the cache_invalidate() was invalidating the changes made in the wizard as well, make it impossible to set any value other than the default one, even though the preview entry was updated accordingly. That also prevented to simply validate the wizard as the accrual account was required but reset anytime we changed its value. * the preview_data field was incorrectly set as Binary while the widget only supports Text -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents employee shifts from being stretched across multiple days when browser and employee time zones differ. It keeps planned hours aligned with the employee's expected daily working time, reducing scheduling mistakes and payroll or staffing confusion.
Original PR description
Description of the issue/feature this PR addresses: The search range for the closest work time is not assigned any value if the start date is different than the end date. The dates can be different…
Description of the issue/feature this PR addresses: The search range for the closest work time is not assigned any value if the start date is different than the end date. The dates can be different if the employee is in another timezone. Current behavior before PR: If the browser time is UTC+2 and a shift of an employee in UTC+6 is scheduled, the start time in UTC time will be 01/01/2000 22:00 and the end time will be 02/01/2000 21:59:59. Converted to the resource.tz timezone, the start date will become 02/01/2000 and the end date will be 03/01/2000. Due to the date difference, the search range is not assigned a value, the start of the shift will be at the employee start time on 02/01/2000 and the end of the shift will be around lunch break one day later. Desired behavior after PR is merged: The shift of the employee for a certain day doesn't span over two days or exceeds the hours per day for the employee Related to odoo/enterprise#20428 Task-2628876 ref https://github.com/odoo/odoo/pull/75527 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix restores unavailable time indicators in project Gantt views after a related field change caused them to stop working. Project planners can again see when assigned people are unavailable, helping avoid scheduling conflicts.
Original PR description
The `user_id` field was replaced in odoo/odoo#74087 by `user_ids` thus breaking the gantt unavailabilities mechanism. TaskID: 2638525
Timesheet users no longer encounter an error when creating their own timesheet entries. This fix ensures employees can record their work time without needing extra permissions, reducing disruption in daily time tracking.
Original PR description
Currently, when we connect as a user with the timesheet module and try to create a new timesheet entry, it throws an error. After this commit, user can also create their own timesheet. Task-Id : 2629541