Friday, February 16, 2024
11 changes · 17.0
Resolved issues and error corrections
When employees or HR teams set a custom number of hours on an accrual-based time off allocation, that value is now kept when saving or validating the allocation. This prevents manually adjusted balances from reverting unexpectedly and helps maintain accurate leave records.
Original PR description
To reproduce the issue: - set a leave type and an accrual plan based on hours - create a new accrual allocation on those leave type and accrual - change the date_from so that some hours are accrued - set a custom amount - save or validate - the value should fall back on the initial amount This fix should allow to keep the custom amount set by the user. task-3615695
This update improves how appointment types are displayed on the appointment page by automatically sorting published appointments first. This makes it faster and easier for staff to find and access the most important appointments without having to search through unpublished options.
Original PR description
This PR changes the order of appointment types on the appointment page based on the appointment's published status. This makes it easier for internal users to access published appointments first. Task-3725160
This update fixes missing translations for three key terms ("gain", "loss", and "gain/loss") in the asset modification wizard. These terms are now properly translated for users in different languages, ensuring a consistent and professional experience across the accounting asset management features.
Original PR description
Fix translation for account_asset / wizard There was fixed strings without translation - gain - loss - gain/loss
This fix corrects the error message that appears when a subscription code is already linked to another database. Previously, the message wasn't displaying properly, making it unclear to users what action to take. Now the helpful guidance message will display correctly, improving the user experience when managing subscription codes across multiple databases.
Original PR description
When a subscription code is already linked to a database and you try to use it on another database, the message displaying that this subscription code is already used and provides the informations of what to do is not correctly displayed. Forward-Port-Of: odoo/enterprise#56618 Forward-Port-Of: odoo/enterprise#47326
This update adds the required XML declaration to the Belgian intrastat XML report. A Belgian partner identified that the XML report was missing the proper XML declaration header, which is now included to ensure compliance with XML standards and partner requirements.
Original PR description
We got a feedback from a Belgian partner that we don't have a xml declaration in the xml report. opw-3745820 Forward-Port-Of: odoo/enterprise#56764 Forward-Port-Of: odoo/enterprise#56727
This update changes how Odoo organizes its internal module list from an unpredictable set to a sorted list. This ensures that tests run consistently and reliably, fixing issues where security tests were failing randomly due to module order variations. The change is internal and won't affect how users interact with Odoo.
Original PR description
Make the set() of module sorted, aka a list. We can be pretty sure that nobody relied on the order of this set before since it was completely underterministic. Therefore this change should not break anything and make the testing on runbot more consistant. This is mainly following the issue with the sql-injection testing failing randomly with the order of the modules. Forward-Port-Of: odoo/odoo#154140
This update fixes access control settings for Polish tax office information in the accounting module. A field that references tax office data now properly enforces the same access restrictions as the underlying tax office model, making the system more secure and eliminating test warnings.
Original PR description
The model `l10n_pl_tax_office` has a group to be able to access it. The Many2one that refers to it, `l10n_pl_reports_tax_office_id`, does not. Currently, it is not really an issue as the accounting's settings are invisible if you don't have the group, but it creates a warning in a test and is more robust Linked to runbot error 24602, 24721 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#154215 Forward-Port-Of: odoo/odoo#153660
This update prevents the web interface from crashing when it encounters permission errors while checking stylesheets for compilation issues. The system now gracefully handles these errors instead of failing, ensuring a more stable user experience when stylesheet features are restricted.
Original PR description
This commit follows [1], which attempted to fix CORS errors occurring when we access the `cssRules` property of stylesheets, to detect scss compilation errors and display a warning to the user. [1] doesn't seem to be enough, as we faced another source of CORS errors. Indeed, in non-secure http, the error is raised even if the origin is the same. We never want this access to crash anyway, as it's a nice to have feature, and if reading `cssRules` is forbidden, there's nothing the user can do anyway. For those reasons, we decided to simply protect the code with a try/catch. [1] odoo/odoo#152696 opw 3746910 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
Documentation and clarification updates
This update adds a signed individual contributor license agreement document. It helps ensure the contributor's work can be legally included in Odoo and supports the related enterprise pull request process.
Original PR description
signing the Odoo Individual Contributor License to fix this one https://mergebot.odoo.com/odoo/enterprise/pull/56718
Miscellaneous changes
This commit addresses the issue where the Product Configurator Popup was displayed unnecessarily when there was only one value for each attribute of a product. The implementation now includes a check to ensure that the popup is shown only when there are more that one choices available. This enhancement improves the user experience by avoiding the display of a redundant popup without viable options. owp-3621666 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/
Original PR description
This commit addresses the issue where the Product Configurator Popup was displayed unnecessarily when there was only one value for each attribute of a product. The implementation now includes a check to ensure that the popup is shown only when there are more that one choices available. This enhancement improves the user experience by avoiding the display of a redundant popup without viable options. owp-3621666 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#154221 Forward-Port-Of: odoo/odoo#145966
A contributor has signed the Contributor License Agreement (CLA) required for submitting pull requests to Odoo. This is a standard legal requirement that allows Odoo to accept and incorporate community contributions while protecting both the project and the contributor.
Original PR description
CLA for enterprise PR --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr