Wednesday, December 20, 2023
11 changes · master
Enhancements to existing features
This update refines how Discuss channels are folded or expanded in Odoo Enterprise. It helps keep the messaging interface behavior consistent and easier to use, with added test coverage to prevent regressions.
Original PR description
follow-up of https://github.com/odoo/odoo/pull/145905 community: https://github.com/odoo/odoo/pull/146674
The salary offer process now checks whether an applicant or employee has an email address before sending an offer. This prevents failed or confusing offer-sending attempts by showing a clear error when contact details are missing.
Original PR description
Steps To Reproduce: --------------- 1. Install Salary Configurator 2. Go to Recruitment 3. Create an applicant 4. Make the email field empty 5. Go to Generate Offer 6. No validation is shown for an empty email I made the following modifications in this commit. --------------------- If the applicant's or employee's email is unavailable, an error message will be displayed when sending the offer to them. task-3431995
Swiss payroll now shows only the relevant marital status options for the employee's localization instead of combining options from multiple localizations. This keeps employee records clearer and reduces the chance of selecting an incorrect status.
Original PR description
We've now moved the selection options within a dedicated function. This ensures that with each new localization, only the default options plus the options specific to that localization are displayed, preventing the accumulation of all options on top of each other. Task-3478191 related PR on odoo: https://github.com/odoo/odoo/pull/133999
The appraisal list now shows each employee's department and groups records by department by default. This makes it easier for managers and HR teams to review appraisals by organizational area without extra setup.
Original PR description
In this PR, - Added department field on an appraisal to start list view - Set Department as the default filter task-3541390
Miscellaneous changes
Recent changes in how the ORM works in 17.0 have made it so when computing `allowed_parent_ids`, the <activity.campaign> record of the new activity is a NewID record instead of a regular record in prior versions. Additionally this seems to lead to the campaign not being aware of its stored `marketing_activity_ids`, which means they cannot be added to `allowed_parent_ids` which means they are then filtered out by the domain in the form view of activities. A temporary solution is to use th
Original PR description
Recent changes in how the ORM works in 17.0 have made it so when computing `allowed_parent_ids`, the <activity.campaign> record of the new activity is a NewID record instead of a regular record in prior versions. Additionally this seems to lead to the campaign not being aware of its stored `marketing_activity_ids`, which means they cannot be added to `allowed_parent_ids` which means they are then filtered out by the domain in the form view of activities. A temporary solution is to use the property `_origin` to force the ORM to use the current record instead of what it believes is the new one. task-3643719 Forward-Port-Of: odoo/enterprise#52957
Some error message parameters were missing for the `move_to` operation, preventing the user from seeing the article name related to the erroneous operation. task-3640010 Forward-Port-Of: odoo/enterprise#52979 Forward-Port-Of: odoo/enterprise#52761
Original PR description
Some error message parameters were missing for the `move_to` operation, preventing the user from seeing the article name related to the erroneous operation. task-3640010 Forward-Port-Of: odoo/enterprise#52979 Forward-Port-Of: odoo/enterprise#52761
Steps: - Open timesheet - Click the start button - In the task field, enter the non-existing task name - Select 'Create and Edit' Issue: - If we haven't selected any project and directly try to create a new task, the project shown is 'Private'. Cause: - The newly created task doesn't belong to any project. The project id is not found. Fix: - Apply the 'task_with_hours' widget, so that if the project id is not found then it doesn't allow the user to create a new task. task-3378
Original PR description
Steps: - Open timesheet - Click the start button - In the task field, enter the non-existing task name - Select 'Create and Edit' Issue: - If we haven't selected any project and directly try to create a new task, the project shown is 'Private'. Cause: - The newly created task doesn't belong to any project. The project id is not found. Fix: - Apply the 'task_with_hours' widget, so that if the project id is not found then it doesn't allow the user to create a new task. task-3378532 Forward-Port-Of: odoo/enterprise#52495 Forward-Port-Of: odoo/enterprise#42971
https://github.com/odoo/enterprise/pull/52634 introduced the possibility to save the token of full payment on renewal. Since saas-16.3 the token must be retrieved with sudo. taskid: 3499685 Forward-Port-Of: odoo/enterprise#53049 Forward-Port-Of: odoo/enterprise#52939
Original PR description
https://github.com/odoo/enterprise/pull/52634 introduced the possibility to save the token of full payment on renewal. Since saas-16.3 the token must be retrieved with sudo. taskid: 3499685 Forward-Port-Of: odoo/enterprise#53049 Forward-Port-Of: odoo/enterprise#52939
Prior to this commit, if you try to invoice a new contact created in the PoS, but forgot to put his RUT, then you get an error and it gets stuck there "thinking". This commit adds the RUT number to the required fields in the chilean localization of the PoS, so that it is not possible to invoice without it. This commit also adapts the partner_editor override in the chilean and mexican localization to adapt it to the fix of the community branch. This fix makes it impossible for a user to mo
Original PR description
Prior to this commit, if you try to invoice a new contact created in the PoS, but forgot to put his RUT, then you get an error and it gets stuck there "thinking". This commit adds the RUT number to the required fields in the chilean localization of the PoS, so that it is not possible to invoice without it. This commit also adapts the partner_editor override in the chilean and mexican localization to adapt it to the fix of the community branch. This fix makes it impossible for a user to modify commercial fields of a child partner. task-id: 2810741 Forward-Port-Of: odoo/enterprise#52885 Forward-Port-Of: odoo/enterprise#52775
Before this PR, within the "Measures" button, We have provided both the "Average Rating" and the "Rating (/5)" as both of measures representing rating values. Therefore, we don't need "Average Rating" in the "Measures" dropdown menu any further. In this PR: removed the "Average Rating" field from the "Measures" dropdown menu. task-3475975 Forward-Port-Of: odoo/enterprise#46458
Original PR description
Before this PR, within the "Measures" button, We have provided both the "Average Rating" and the "Rating (/5)" as both of measures representing rating values. Therefore, we don't need "Average Rating" in the "Measures" dropdown menu any further. In this PR: removed the "Average Rating" field from the "Measures" dropdown menu. task-3475975 Forward-Port-Of: odoo/enterprise#46458
In this commit, we revert the below commit because l10n_hr_in_payroll is not dependent on hr_contract_salary module. commit-https://github.com/odoo/enterprise/pull/50365/commits/5588df97a956e5f83a4c4b7bc7d669c198ddbd40 task-3493469 Forward-Port-Of: odoo/enterprise#53067 Forward-Port-Of: odoo/enterprise#52938
Original PR description
In this commit, we revert the below commit because l10n_hr_in_payroll is not dependent on hr_contract_salary module. commit-https://github.com/odoo/enterprise/pull/50365/commits/5588df97a956e5f83a4c4b7bc7d669c198ddbd40 task-3493469 Forward-Port-Of: odoo/enterprise#53067 Forward-Port-Of: odoo/enterprise#52938