Daily updates from Odoo
Friday, December 5, 2025
12 changes
1 change
Enhancements to existing features
This update clarifies the labeling of a field used during salary adjustments within the HR payroll module. The change ensures users understand exactly where this input type is accessible, improving the overall user experience. This is a minor improvement focused on usability.
Original PR description
This change ensures the label accurately reflects where the field is accessible and providing better clarity for users when working with salary adjustments. Task: 5375187 Forward-Port-Of: odoo/enterprise#101065
2 changes
Enhancements to existing features
This update clarifies the labeling of a field used when making salary adjustments within the HR payroll module. The change ensures users understand exactly where this input is accessible, improving the overall user experience. This is a minor improvement focused on usability.
Original PR description
This change ensures the label accurately reflects where the field is accessible and providing better clarity for users when working with salary adjustments. Task: 5375187 Forward-Port-Of: odoo/enterprise#101065
This update simplifies the process of customizing sign templates within Odoo. A new method allows developers to more easily modify or add fields to these templates, making it simpler to adapt them to specific business needs. This change improves flexibility and reduces the effort required for template adjustments.
Original PR description
Introduced a dedicated _getTemplateFields() method to make easier to override or extend the fields in patches. Forward-Port-Of: odoo/enterprise#95722
1 change
Enhancements to existing features
This update clarifies the labeling of a field used when making salary adjustments within the Odoo Enterprise system. The change ensures users understand exactly where this setting is accessible, improving the overall user experience and reducing potential confusion. This is a minor improvement focused on usability.
Original PR description
This change ensures the label accurately reflects where the field is accessible and providing better clarity for users when working with salary adjustments. Task: 5375187 Forward-Port-Of: odoo/enterprise#101065
2 changes
Enhancements to existing features
This update clarifies the labeling of a field used when making salary adjustments within the HR payroll system. The change ensures users understand exactly where this setting is accessible, improving the overall user experience. This is a minor improvement focused on usability.
Original PR description
This change ensures the label accurately reflects where the field is accessible and providing better clarity for users when working with salary adjustments. Task: 5375187 Forward-Port-Of: odoo/enterprise#101065
This update enhances the user experience on the Frontdesk module by clarifying messages displayed when a report is empty. The changes improve readability and provide a better experience for users viewing an empty report screen, ultimately contributing to a more intuitive interface.
Original PR description
Updating the frontdesk empty screen messages for clarity and improving user experience when viewing an empty report screen. Task: 5380402
3 changes
Enhancements to existing features
This update enhances the ability to retrieve information from related records (o2m relationships) when sending sign requests. Previously, limitations prevented accessing additional data, but this change enables greater flexibility and data access for sign workflows. This improves the functionality of the sign process.
Original PR description
The class `SignerX2Many` is inheritable, but if we need another value from the o2m, we can't use it because the `signerX2Many` is not exportable. Enable `signerX2Many` customization, allowing more fields to be read from the `sign.send.request.signer` model. Forward-Port-Of: odoo/enterprise#99977
This update clarifies the labeling of a field used when making salary adjustments within Odoo. The change ensures users understand exactly where this input type is accessible, preventing confusion and streamlining the adjustment process. This improves the overall user experience for HR professionals.
Original PR description
This change ensures the label accurately reflects where the field is accessible and providing better clarity for users when working with salary adjustments. Task: 5375187 Forward-Port-Of: odoo/enterprise#101065
This update enhances the reliability of our access rights tests by replacing manual data manipulation with a more robust method. Previously, tests were fragile and prone to breaking due to changes in Odoo's data models. This change ensures tests are more stable and accurately reflect access control rules.
Original PR description
In our tests for access rights, we manually do CRUD operations to check them. However, this approach is difficult to maintain and highly susceptible to changes in model fields. Therefore, we are switching to using has_access function for more robust verification.
2 changes
Enhancements to existing features
This update introduces a new cron job to automatically move attachment files from the server to cloud storage. This improves storage efficiency and reduces server load. Users can manually trigger this process to ensure all attachments are migrated.
Original PR description
This commit provides a cron job to migrate attachment binary to the cloud storage. The cron job is designed to be manually triggered from by the "Run Manually" button of the Scheduled Action's form…
This commit provides a cron job to migrate attachment binary to the
cloud storage. The cron job is designed to be manually triggered from
by the "Run Manually" button of the Scheduled Action's form view.
The cron job will try to upload some attachments once
1. size is greater than the minimum upload file size defined by
(ir.config_parameter: cloud_storage_min_file_size)
2. id is greater than the number defined by
(ir.config_parameter: cloud_storage_migration_min_attachment_id)
3. res_model is in a white list
(ir.config_parameter: cloud_storage_migration_message_models)
(ir.config_parameter: cloud_storage_migration_all_models)
4. not used by documents.document
optional configurations to avoid timeout issues
- cloud_storage_migration_max_file_size:
max bytes for each migrated attachment
- cloud_storage_migration_max_batch_file_size:
max total bytes for migrated attachments in one cron job execution
The cloud_storage_migration_min_attachment_id which can be accessed
from the list view can be treated as the progress of the cron job.
Manually setting it to 0 and retriggering the cron job will retry the
upload process for previously failed or ignored attachments.
taskid: 5387110
Steps
1. install a cloud storage module (cloud_storage_google, cloud_storage_azure)
2. install the cloud storage migration module (cloud_storage_migration)
3. Go to Settings for Cloud Storage Settings <img width="505" height="206" alt="image" src="https://github.com/user-attachments/assets/d72d7b52-5ce7-4209-8645-4a8ac35dd049" />
4. [Configure the cloud storage settings](https://www.odoo.com/documentation/19.0/applications/general/integrations/cloud_storage.html)
5. Setting the Minimum File Size. Attachments smaller than the size won't be uploaded to the cloud storage <img width="457" height="96" alt="image" src="https://github.com/user-attachments/assets/8dc4e6fe-9c84-44f5-a83a-28c7b2fad30a" />
6. After 4, configure settings for the cloud storage migration
a. <img width="464" height="209" alt="image" src="https://github.com/user-attachments/assets/37352453-ff0e-4e03-a4d5-7fdb8168dee1" />
b. Cron Job:
i. the link to the cloud storage migration cron job
ii. the cron job is designed to be a job only triggered by clicking "Run Manually".
iii. It will re-trigger itself until all relevant attachments are migrated.
c. Parameters:
<img width="882" height="571" alt="image" src="https://github.com/user-attachments/assets/9926ed9f-81ac-4917-b759-872ed2584217" />
d. Progress Bar:
i.progress of the migration job
ii. calculated by `cloud_storage_migration_min_attachment_id / cloud_storage_migration_max_attachment_id`
e. Attachment Report:
i. <img width="1907" height="298" alt="image" src="https://github.com/user-attachments/assets/33a77835-c6b6-4bc4-b20a-4ec68acba783" />
ii. a view to help administrator analyze which model's attachments should be migrated
iii. help to configure step 6.c.i.4 and step 6.c.i.5
f. Message Attachments
i. help to configure step 6.c.i.4
g.All attachments
i. help to configure step 6.c.i.5
7. Click Cron Job and then Click Run Manually
<img width="409" height="123" alt="image" src="https://github.com/user-attachments/assets/f60cdfcf-e6a6-4503-87fc-0be7f14ceede" />
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-prThis update ensures that tax amounts are included in invoice data sent to the government for reporting purposes. As companies pay taxes and can later claim refunds, accurately reflecting the total tax value in export documents is now required. This change supports proper tax reporting and compliance.
Original PR description
Following the task- https://www.odoo.com/odoo/project.task/4878805 and PR- https://github.com/odoo/odoo/pull/213931 Here we are not collecting tax from the customer but the company has pay taxes to the goverment and after that the company can claim refund for the taxes. So when we are sending data to goverment then we need to include tax part into the invoice total task-5369117 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
1 change
Enhancements to existing features
This update ensures that newly imported partner records are automatically identified as 'companies' within Odoo. This is crucial for accurate accounting and reporting related to electronic invoices (UBL-CII) and simplifies the process of matching imported transactions with company data. It addresses a previous issue where imported partners weren't correctly categorized.
Original PR description
Ensure imported partner records are marked as companies when creating new partners. Task-5353923 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr