Thursday, April 3, 2025
4 changes · saas-18.2
Resolved issues and error corrections
This fix helps the accounting mail gateway correctly identify records when processing incoming emails. It reduces the risk of misrouted or failed email-based accounting actions, improving day-to-day reliability for users who work with vendor bills, invoices, or related messages by email.
Original PR description
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
Fixes an issue where creating a new Gamification challenge could trigger an error before users could complete the form. This helps administrators use Gamification settings reliably without encountering terminal errors during setup.
Original PR description
Currently, an error occurs when opening a new gamification challenge. Steps to Reproduce: --- - Install the `Gamification` application - Setting > Gamification Tools > Challenges - Click NEW - Error in Terminal Traceback: --- NotImplementedError At [1], an incorrect domain was passed, which led to a NotImplementedError at [2]. After this commit - https://github.com/odoo/odoo/commit/4f13b617547a27c714af69529cf69d799bdb601c#diff-0346840e191cc12e28d8578cf78319e2bf932324ef9c7a270f14e5093064ff57 [1]- https://github.com/odoo/odoo/blob/1731c2aa14b0630c0a8a3505cbaa202776bac280/addons/gamification/models/gamification_challenge.py#L70 [2]- https://github.com/odoo/odoo/blob/1731c2aa14b0630c0a8a3505cbaa202776bac280/odoo/addons/base/models/res_groups.py#L216-L217 sentry-6474367890 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where refusing a newly created recruitment application with missing applicant details could cause an error. Recruiters can now refuse incomplete applications without the process being interrupted.
Original PR description
Currently, a traceback is occurring when trying to refuse an application. To reproduce this issue: 1) Install `hr_recruitment` 2) Open any job position 3) Create a new application record 4) Don't…
Currently, a traceback is occurring when trying to refuse an application. To reproduce this issue: 1) Install `hr_recruitment` 2) Open any job position 3) Create a new application record 4) Don't give any values and click on refuse button Error:- ``` TypeError: sequence item 0: expected str instance, bool found ``` This issue was occurring because of the refactoring from the below commit https://github.com/odoo/odoo/pull/169955/commits/e9bad7ebc795c34052a667a227c2103aa58fb861 When the user clicks on the refuse button, `_compute_applicant_without_email` method triggers with the applicant as a new origin object. Partner_name is not a required field and the applicant is a new origin object, So indeed we won't get any value for `display_name` or `partner_name`. This leads to the above traceback from the below line https://github.com/odoo/odoo/blob/1a1354727f965b018374aa2001b0bb7f981d1cc1/addons/hr_recruitment/wizard/applicant_refuse_reason.py#L38-L42 sentry-6409185730
When Belgian salary contract users clear the “Other dependent” option, related dependent details are now removed as well. This prevents hidden dependent values from remaining on employee records and keeps the salary package information consistent with the backend behavior.
Original PR description
When you uncheck the 'Other dependent' box, it keeps the value in the dependent fields. This leads to have values set on the employees that are not visible. To avoid this issue, we empty the 'dependent' fields when we uncheck the 'Other Dependent' checkbox. This is the same behaviour of what is done in the onchange on backend view.