Monday, March 18, 2024
14 changes · 17.0
Enhancements to existing features
This pull request updates the Account module with improvements to logos, login templates, and custom addons configuration. The changes include updates to multiple language translation files and module manifest, ensuring the accounting system is properly localized and branded across all supported languages.
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
Resolved issues and error corrections
Fixes an issue where selecting a project while adding a task from a contact form could reset the project to private and prevent changes. This helps users working with customized contact forms keep the intended project assignment without extra corrections.
Original PR description
## Issue:
- user can't edit the project when project tasks are added as a o2m field to a contact form using studio.
## Steps to reproduce:
- create a project.
- In a contact form open Studio and add a O2M field Customer (Task)
- Add a line in the O2M and set Project to the one you created.
- On save notice that the project is reset to private and that you
can't change it
## Explantion:
- `project_id` is not passed to the `web_save` method, because it is readonly.
opw-3713885
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prDocumentation and clarification updates
A contributor has signed the Odoo Individual Contributor License Agreement (CLA) on March 4, 2024. This is a standard legal requirement that allows Odoo to use contributions from community members while protecting both the contributor and the company.
Original PR description
Sign the Odoo CLA
The restaurant point-of-sale demo data now includes an example product with multiple variants, each carrying its own price. This helps businesses and evaluators better understand how variant pricing works in restaurant scenarios during demos or onboarding.
Original PR description
**Purpose of this commit:** Added demo data to demonstrate multi-variant of a product where each product-variant have a different price. task-3617006
This update improves the performance of the Brazilian EDI module by fixing how certain features are calculated and displayed. The changes separate visibility logic from email field processing and remove unnecessary system triggers, resulting in faster and more efficient document handling without affecting user-facing functionality.
Original PR description
- Whether the option is visible or not shouldn't depend on the `mail_extra_fields` compute. Use a separate compute to avoid useless processing. - Wrong moves used in the warning computation. - Remove useless trigger in `api.depends` to avoid unecessary computations.
This update corrects the positioning of the message that appears when marking timesheets as billable or non-billable in project tasks. The message was appearing in the wrong location due to an imprecise technical selector, which has now been fixed to display correctly.
Original PR description
Versions: --------- - 17.0 Issue: ------ Message for flag timesheet from project as billable/non-billable is misplaced. Cause: ------ Xpath given for Message placed in sale_timsheet is not very specific. Solution: --------- Give accurate xpath for message div. task-3630449
This update corrects the display order of company identification numbers in Czech Republic reports to match local standards. The Company ID (IČO) now appears before the VAT ID (DIČ), and the label has been clarified to "Company ID" for better clarity. This is a minor formatting adjustment to report templates with no impact on system functionality.
Original PR description
In Czech republic, the standard is to first render Company ID (IČO), and then to render VAT ID (DIČ). What I did in this commit is: - changing the position to before (not after), so company ID renders before VAT ID - I changed a label from ID to Company ID (so it is obvious in what ID it is) - This should not cause any harm, as we are just doing tiny changes in a view, not changing any logic. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects the display order of company identification fields on Czech invoices to comply with local standards. The Company ID (IČO) now appears before the VAT ID (DIČ), and the label has been clarified to "Company ID" for better clarity. This is a minor formatting adjustment to the invoice report template with no impact on business logic or data.
Original PR description
In Czech republic, the standard is to first render Company ID (IČO), and then to render VAT ID (DIČ). What I did in this commit is: changing the position to before (not after), so company ID renders before VAT ID I changed a label from ID to Company ID (so it is obvious in what ID it is) This should not cause any harm, as we are just doing tiny changes in a view, not changing any logic. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes a test that was failing intermittently due to timing issues. The test now properly waits for WebSocket connections to be fully established before checking results, ensuring more reliable testing and fewer false failures in our quality assurance process.
Original PR description
Before this commit, the `test_websocket_instances_weak_set` was sometimes failing. Indeed, this test doesn't wait for the connection to be fully established before making its assertions. This commit fixes this issue. fixes runbot-55037,55035 Forward-Port-Of: odoo/odoo#157433
This update fixes the display order of company identification numbers on Czech invoices to match local standards. Company ID (IČO) now appears before VAT ID (DIČ), and the label has been clarified from "ID" to "Company ID" for better clarity. This ensures invoices comply with Czech business practices.
Original PR description
In Czech republic, the standard is to first render Company ID (IČO), and then to render VAT ID (DIČ). - Changing the position to before (not after), so company ID renders before VAT ID. - Changed label from "ID" to "Company ID" (so it is obvious in what ID it is). Original fixes by @cunivca: odoo/odoo#149339, odoo/odoo#149340, merged into one. Related: https://github.com/odoo/odoo/commit/d0704a19de31e0251d343081ae6b3da9991a248e
A new contributor (hari1119) has signed the individual Contributor License Agreement (CLA) required to contribute to the Odoo project. This is a standard legal requirement that allows the contributor to submit code changes to the repository.
Original PR description
Signed a individual CLA
A contributor has signed the Odoo Contributor License Agreement (CLA), which is a legal requirement for all code contributions to the Odoo project. This signature confirms the contributor's agreement to the terms and conditions for submitting code to the repository.
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
A contributor has signed the Contributor License Agreement (CLA) required to contribute to Odoo. This is a standard legal requirement that allows the contributor to submit code changes to the Odoo project. The signature has been recorded in the CLA documentation.
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
A contributor (santiagopim) has signed the Odoo Contributor License Agreement (CLA), which is a legal requirement for all code contributions to the Odoo project. This enables the contributor to submit code changes to the repository going forward.
Original PR description
Description of the issue/feature this PR addresses: Sign CLA agreement for santiagopim Current behavior before PR: No CLA signed Desired behavior after PR is merged: CLA signed --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr