Daily updates from Odoo
Wednesday, February 21, 2024
12 changes
8 changes
Enhancements to existing features
The Documents app search panel has been updated to work better on mobile devices and stay aligned with recent platform changes. This should make browsing and filtering documents on smaller screens smoother and more consistent for users.
Original PR description
This commit adapts the documents customization of the search panel to follow changes made in https://github.com/odoo/odoo/pull/149246 task-3644159
This update adds support for e-commerce operator reporting in India’s GSTR-1 process, including the relevant Table 14 information. It helps businesses prepare more complete GST filings and includes cleanup to make the reporting logic easier to maintain.
Original PR description
Related PR-https://github.com/odoo/odoo/pull/153070 task-3672448
Luxembourg payroll rules and related parameters have been adjusted to reflect changes that apply in 2024. This helps ensure employee salary calculations remain accurate and aligned with current local requirements.
Spreadsheets can now use the company’s custom branding colors directly from the color picker. This makes it easier for users to create reports and documents that match the company identity without manually recreating colors.
Original PR description
With this commit, the company custom colors (for the documents/reports layout, and emails) now appears in the spreadsheet color picker as custom colors. It allows to easily create spreadsheets with the company identity. Task: 3707769
Project-related features now identify completed tasks using a shared “closed” status rather than specific task state values. This makes task filtering more consistent across field service, planning, holidays, sales forecasting, and enterprise project features, reducing mismatches in reports and workflows.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/149805 Task-3681837
Planning settings now separate two mutually exclusive options: employees can either switch shifts with colleagues or unassign themselves from shifts. This makes the available scheduling behavior clearer for administrators and keeps the default behavior focused on shift switching.
Original PR description
Before this commit, it was not clear to users that the 'switch shifts' feature existed, and that is it mutually exclusive with the 'allow unassignment' option in the Planning settings. To make things clear, this commit splits the 'allowing unassignment' setting in two: - The 'switch shifts with other employees' option which corresponds to the current behavior when the 'allow unassignment' feature is disabled. It is the default value. - The 'unassignment themselves from shifts' option which corresponds to the current behavior when the 'allow unassignment' feature is enabled. task-3703648
Planning users now see a clear pop-up when changing the time, date, or recurrence settings of a recurring shift from the calendar. This helps them choose how the change should apply, reducing accidental updates across multiple planned shifts.
Original PR description
In this PR, when trying to modify the time, date, or recurrence settings for a planned shift from the calendar view, a pop-up dialog will be displayed. Within this dialog, you can choose the desired options for the shifts task-3502065
Users with access to multiple companies can now choose and change the company on approval requests, making requests easier to manage across organizations. Approval lists also show company and approver information more clearly, and the approve button is easier to interpret depending on whether documents are attached.
Original PR description
This commit adds the possibility for user to select the company for which he wants to create an approval request if they have the multi company access rights. Also, the company field is added in the approval request form view and it's now writable to make the user able to change the company of the approval request if needed. the company field is also added in the approval request tree view for better visibility. In addition to that, this commit adds a small ux improvement for the approve button to make it more visible or less visible depending if a document has been attached to the approval request or not. For the tree view, the approvers are now displayed to be visible for the user. task-3632010
4 changes
Enhancements to existing features
This update ensures that financial reports in Chile use the correct local terminology for "Untaxed Amount" (translated as "Monto neto" instead of the Spain/LATAM standard). The change applies across multiple sales and accounting modules to maintain consistent and accurate financial reporting for Chilean customers. Unnecessary untranslated entries have also been removed to improve file clarity.
Original PR description
In Chile, "Untaxed Amount" has its own special term that isn't used in Spain/LATAM spanish: ~~"Total neto"~~ "Monto neto" [as for v17 since customer changed their mind]. Therefore everywhere that it appears (in a .pot file), we ensure that the es_CL localization uses this term. Also untranslated terms from the es_CL.po files that were edited have been removed since they add no benefit and make it harder to read the file (we expect to only add terms to the file, not translate every term for Chile). opw-3670297 Forward-Port-Of: odoo/enterprise#54939 Forward-Port-Of: odoo/enterprise#54712
This update improves the Belgian payroll system's performance by preventing unnecessary reloading of web interface files when automated payroll tasks run. The change removes certain files from the update process, allowing payroll operations to complete more quickly without disrupting the user experience.
Original PR description
This commit is aimed at avoiding the reloading of the webclient assets when the cron is run. This is done by removing files from the _get_data_files_to_update method. task-3607711 Forward-Port-Of: odoo/enterprise#54120
This update ensures that the "Untaxed Amount" field displays the correct Chilean Spanish term "Monto neto" across multiple financial and operational modules. The change improves localization accuracy for Chilean users by using region-specific terminology that differs from standard Spanish. Unnecessary untranslated entries were also removed from Chilean translation files to improve clarity.
Original PR description
In Chile, "Untaxed Amount" has its own special term that isn't used in Spain/LATAM spanish: ~~"Total neto"~~ "Monto neto" [as for v17 since customer changed their mind]. Therefore everywhere that it appears (in a .pot file), we ensure that the es_CL localization uses this term. Also untranslated terms from the es_CL.po files that were edited have been removed since they add no benefit and make it harder to read the file (we expect to only add terms to the file, not translate every term for Chile). opw-3670297 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#150683 Forward-Port-Of: odoo/odoo#150141
This update allows companies to prevent automatic propagation of manager-level access rights to all employees when installing new modules. Previously, all existing employees would automatically receive the same access rights as the Default Template User. Now administrators can disable this behavior by setting a configuration option, giving companies more control over user permissions and security.
Original PR description
When installing a new module, the access of the Default Template User is propagated to any existing employee (introduced at aefb05eb497a8a16a). This can be problematic in companies that don't want all their employees to become manager by default. Allow to disable this behaviour in a settings. This is the version of the patch targetting stable version that is not configurable through the interface, manually creating an ICP base_setup.default_user_rights_minimal=True as the way to change the behaviour. Closes odoo/odoo#149224 Task-id 3685856 Forward-Port-Of: odoo/odoo#150391