Daily updates from Odoo
Navigate
Branch
Tuesday, March 1, 2022
14 changes
Enhancements to existing features
Belgian payroll setup now creates resource calendars in batches instead of one by one. This improves setup performance and reduces processing time for companies configuring payroll data.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/85532
The Field Service demo environment now includes more realistic projects and tasks across stages, dates, billing states, worksheets, timesheets, subtasks, activities, tags, ratings, and completed reports. This makes demonstrations and testing closer to real business workflows, especially for planning, invoicing, reporting, and task analysis.
Original PR description
In this task: - An fsm project added configured at employee rate with many tasks at different stages. - Some tasks are recurrent, archived, to invoice - Another worksheet template added and used with some tasks - For some tasks, we add initially planned hours, timesheets, sub-tasks and timesheets on these sub-tasks, activities were scheduled, tags added and the status is either 'blocked' or 'ready', ratings added - Data added for the working hours/days to assign/close metrics of the tasks analysis report - Some tasks marked as done with worksheets, products, sent and signed reports, linked to an SO Task-id : 2680425
Code cleanup and technical improvements
Gantt chart dependency handling has been moved into the shared Gantt component so it can be reused beyond Projects. Scheduling behavior is now more cautious around complex linked tasks, reducing the risk of unwanted date changes while keeping Project-specific extensions available.
Original PR description
This commit moves the dependency mecanism that had been developed in
project_enterprise into web_gantt.
This commit creates a basic rescheduling behavior in web_gantt that can
be extended in other modules (as it is done for project_enterprise in
this commit).
An additional module `test_web_gantt` has been created in order to test
the the rescheduling feature on some fake models.
Functionaly wise, we reduced the scope of the rescheduling algorithm, in
order to prevent undesired results. This commit prevents rescheduling
so called `loops` when it detects that it can not solve them. `Loops`
are not cyclic dependencies but records that are linked together, forming
a loop, as illustrated here below:
------> 4
| |
| v
1 -> 2 ->3
task-2691454
see also:
- https://github.com/odoo/documentation/pull/1529
- https://github.com/odoo/odoo/pull/85395Several business application screens were updated to use a compatibility layer while the user interface framework evolves. This keeps existing approval, document, spreadsheet, barcode, timesheet, dashboard, cohort, project, and signing features working reliably without changing their business behavior.
Original PR description
This PR replaces `Component` by `LegacyComponent` when the component uses owl 1's removed features like `el` and `trigger`. If a non legacy component inherits from this class then it should remove the use of those owl 1's removed features and retarget to an usual `Component`. Community PR: https://github.com/odoo/odoo/pull/85389
Miscellaneous changes
before this PR, when map view is default view for a action and action contains any mobile_friendly view then in mobile it open that view instead of map view. after this PR, make map view mobile_fiendly so when map view is default in action it should open map view in mobile and add test case for that feature. task-2740041 Forward-Port-Of: odoo/enterprise#23656
Original PR description
before this PR, when map view is default view for a action and action contains any mobile_friendly view then in mobile it open that view instead of map view. after this PR, make map view mobile_fiendly so when map view is default in action it should open map view in mobile and add test case for that feature. task-2740041 Forward-Port-Of: odoo/enterprise#23656
before this commit, if we use special characters* like (,[ in filter name it will give trace back while renaming. this is happening because we use regular expression and it consider special character like (,[ as part of regular expression in replace method after this commit, f we use special characters* like (,[ in filter name it will not give trace back while renaming. to solve this issue escape all special character in label. *: any escape string - See https://developer.mozilla.o
Original PR description
before this commit, if we use special characters* like (,[ in filter name it will give trace back while renaming. this is happening because we use regular expression and it consider special character like (,[ as part of regular expression in replace method after this commit, f we use special characters* like (,[ in filter name it will not give trace back while renaming. to solve this issue escape all special character in label. *: any escape string - See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions task-2691559 Co-authored-by: Rémi Rahir <rar@odoo.com> Forward-Port-Of: odoo/enterprise#24871 Forward-Port-Of: odoo/enterprise#24566
In https://github.com/odoo/enterprise/commit/a416331849b4406a21726f5f5ea302dd49326f01, forward port of https://github.com/odoo/enterprise/pull/24029 signature change of _fill_missing_values() has not been noticed (param cache is removed). Task: 2752565 Forward-Port-Of: odoo/enterprise#24768
Original PR description
In https://github.com/odoo/enterprise/commit/a416331849b4406a21726f5f5ea302dd49326f01, forward port of https://github.com/odoo/enterprise/pull/24029 signature change of _fill_missing_values() has not been noticed (param cache is removed). Task: 2752565 Forward-Port-Of: odoo/enterprise#24768
L10N Staging fails with an error message: The stamp date and time cannot be prior to the invoice issue date and time. Set a specific invoice date and patch current time to a day after that to avoid date and time inconsistency when running EDI tests in l10n_cl_edi module. Forward-Port-Of: odoo/enterprise#24712
Original PR description
L10N Staging fails with an error message: The stamp date and time cannot be prior to the invoice issue date and time. Set a specific invoice date and patch current time to a day after that to avoid date and time inconsistency when running EDI tests in l10n_cl_edi module. Forward-Port-Of: odoo/enterprise#24712
There is an error when we are trying to print a payslip with an employee with non Latin-1 characters in his name. Because the name of the employee is written in the filename of the payslip. Step to reproduce: - Install the hr_payroll app - create an employee with non-Latin characters in is name - go to the Payslips of this employee - create a new payslip for this employee - and try to print it Current behavior: It's open a new tab and throw a `502 Bad Gateway` error because the tr
Original PR description
There is an error when we are trying to print a payslip with an employee with non Latin-1 characters in his name. Because the name of the employee is written in the filename of the payslip. Step to reproduce: - Install the hr_payroll app - create an employee with non-Latin characters in is name - go to the Payslips of this employee - create a new payslip for this employee - and try to print it Current behavior: It's open a new tab and throw a `502 Bad Gateway` error because the treads for printing the payslips crashes. Behavior after this commit: We are now using the function `content_disposition` to use the percent-encoding defined here: https://www.rfc-editor.org/rfc/rfc3986 opw-2748662 Forward-Port-Of: odoo/enterprise#24795 Forward-Port-Of: odoo/enterprise#24635
This PR sort timesheet rows in alphabetical order for grid view. task-2732325 Forward-Port-Of: odoo/enterprise#23553
Original PR description
This PR sort timesheet rows in alphabetical order for grid view. task-2732325 Forward-Port-Of: odoo/enterprise#23553
When in year mode, it was not possible to get the link if there was not a slot created before in another mode. Fix also the behavior in the year mode when selecting a date. Indeed, selecting a date in year mode create an "allDay" slot. If the user select the same date or a date containing events, it should remove only the "allDay" slot linked to the date. We don't want to remove all events of the date to avoid error of the user. task-2738045 Forward-Port-Of: odoo/enterprise#23563
Original PR description
When in year mode, it was not possible to get the link if there was not a slot created before in another mode. Fix also the behavior in the year mode when selecting a date. Indeed, selecting a date in year mode create an "allDay" slot. If the user select the same date or a date containing events, it should remove only the "allDay" slot linked to the date. We don't want to remove all events of the date to avoid error of the user. task-2738045 Forward-Port-Of: odoo/enterprise#23563
Employees should not be able to request leaves in the past when there's a payslip generated and paid for that period. TaskID: 2764934 Forward-Port-Of: odoo/enterprise#24341
Original PR description
Employees should not be able to request leaves in the past when there's a payslip generated and paid for that period. TaskID: 2764934 Forward-Port-Of: odoo/enterprise#24341
For now the 'subtotal' block doesn't work because it still uses the old system of `amount_by_groups` which existed in 14.0 but was replaced by `tax_totals_json` in 15.0. This commit uses the new `account.document_tax_totals` template to display the widget in the report. opw-2754425 Forward-Port-Of: odoo/enterprise#24649
Original PR description
For now the 'subtotal' block doesn't work because it still uses the old system of `amount_by_groups` which existed in 14.0 but was replaced by `tax_totals_json` in 15.0. This commit uses the new `account.document_tax_totals` template to display the widget in the report. opw-2754425 Forward-Port-Of: odoo/enterprise#24649
Purpose of this PR to set sale order line field default for slot depending sale order line set on task or project of that slot. So, in this PR remove extra code that stop compute of sale_line_id to get value from task or project. task-2732325 Forward-Port-Of: odoo/enterprise#23374
Original PR description
Purpose of this PR to set sale order line field default for slot depending sale order line set on task or project of that slot. So, in this PR remove extra code that stop compute of sale_line_id to get value from task or project. task-2732325 Forward-Port-Of: odoo/enterprise#23374