Thursday, September 12, 2024
19 changes · master
Enhancements to existing features
Australian payroll now uses the shared payroll period calculation method instead of a separate custom list. This keeps pay period handling more consistent and easier to maintain, with no expected change for day-to-day users.
Original PR description
After this commit, instead of using a dictionary, we will use a standard method to get the factors of a pay period in `l10n_au_hr_payroll`. task-4029012
Marketing automation campaign activity cards now display the percentage of messages opened instead of the bounced percentage. This gives marketers a more useful engagement metric directly in the campaign view, helping them assess campaign performance at a glance.
Original PR description
This commit removes the bounced percentage from activity kanban card in the mareting_automation's campaign form view and adds the opened percentage. Task-4125818
Resolved issues and error corrections
This fix aligns asset-related screens with the newer "list" view naming instead of the older "tree" wording. It helps keep the interface and configuration consistent with recent platform changes, reducing small display or compatibility issues.
Original PR description
[FIX] base/ir.ui.view: fix use 'list' instead of 'tree' see: https://github.com/odoo/odoo/pull/159909
Code cleanup and technical improvements
Accounting reports now consistently receive prior report settings instead of sometimes receiving no settings at all. This internal cleanup reduces the risk of reporting errors and makes future maintenance of financial reports easier without changing day-to-day user workflows.
Original PR description
Keeping `previous_options` as None is error-prone and can be made simpler. This commit makes `previous_options` a mandatory parameter. Task ID: 3977823
Miscellaneous changes
…nvoice Before this commit, subscriptions automatic invoices are skipped when the flag pending transactions is set. it is correct to avoid double payment for the same period but there is a problem if the flag stays while the subscription has been renewed since. This commit aimes to remove that flag when an invoice is posted for this subscruption. taskid: 4107185 Forward-Port-Of: odoo/enterprise#69589 Forward-Port-Of: odoo/enterprise#68713
Original PR description
…nvoice Before this commit, subscriptions automatic invoices are skipped when the flag pending transactions is set. it is correct to avoid double payment for the same period but there is a problem if the flag stays while the subscription has been renewed since. This commit aimes to remove that flag when an invoice is posted for this subscruption. taskid: 4107185 Forward-Port-Of: odoo/enterprise#69589 Forward-Port-Of: odoo/enterprise#68713
Fixed a visual issue where WhatsApp partner message bubbles appeared unnecessarily faded. This keeps message bubbles easier to read and consistent with the intended conversation styling.
Original PR description
The WhatsApp partner message bubble had an unnecessary `opacity-25` class assigned. The original purpose of the line was to apply a `light-green` background to the bubble. However, as this would conflict with the existing color formatting for message bubbles, this line has now become redundant.  
This draft refactors automated tour tests across several Odoo Enterprise apps, including accounting, helpdesk, manufacturing, signing, and rental flows. The changes are internal and should help maintain test reliability without changing day-to-day user workflows.
The Helpdesk forum tour relies on the forum containing at least one post. This PR manually creates a post in python before launching the tour. Task-4143944 Forward-Port-Of: odoo/enterprise#69066
Original PR description
The Helpdesk forum tour relies on the forum containing at least one post. This PR manually creates a post in python before launching the tour. Task-4143944 Forward-Port-Of: odoo/enterprise#69066
Currently, when a user requests an invoice from a POS ticket under a Mexican company, the CFDI document attached to the invoice incorrectly uses the buyer's name instead of using the provided company name. ### Steps to reproduce * install `l10n_mx_edi_pos` * Switch to a Mexican company * the settings enable "Generate a code on ticket" * validate a POS order * follow the instructions on the ticket to generate an invoice. Make sure to provide a company name on the customer form. When
Original PR description
Currently, when a user requests an invoice from a POS ticket under a Mexican company, the CFDI document attached to the invoice incorrectly uses the buyer's name instead of using the provided company name. ### Steps to reproduce * install `l10n_mx_edi_pos` * Switch to a Mexican company * the settings enable "Generate a code on ticket" * validate a POS order * follow the instructions on the ticket to generate an invoice. Make sure to provide a company name on the customer form. When checking the XML file that is forwarded to the Mexican tax authorities, you see that only the "individual name" is registered there as the buyer, when it should be the company name. opw-4103543 opw-4071503 Forward-Port-Of: odoo/enterprise#69872 Forward-Port-Of: odoo/enterprise#69126
Steps to reproduce: In field service, have a project on which you have to sell 3 of item A. Item a is tracked by serial number and the delivery route is in 2 steps. From stock to output and from output to customer. On the sale order make sure you have 3 separate lines of 1 quantity of product A separated or not by sections. Confirm this one. This will create two pickings. One picking linked to a global stock move for 3 units from stock to output. A second picking linked to 3 stock moves ea
Original PR description
Steps to reproduce: In field service, have a project on which you have to sell 3 of item A. Item a is tracked by serial number and the delivery route is in 2 steps. From stock to output and from output to customer. On the sale order make sure you have 3 separate lines of 1 quantity of product A separated or not by sections. Confirm this one. This will create two pickings. One picking linked to a global stock move for 3 units from stock to output. A second picking linked to 3 stock moves each linked to a sale line id. Prioritise the first one by starring it. Now go back to the project and mark is as done. Had to redo the tests as from 17.2 one picking is generated at a time. Here we modify rules to create the two pickings. We have to do this to mimic customers migrating from prior versions of 17.2 to later versions. Original closed PR: https://github.com/odoo/enterprise/pull/61079 OPW-4088696 Forward-Port-Of: odoo/enterprise#68801 Forward-Port-Of: odoo/enterprise#68630
### Steps to reproduce: - Install eCommerce and Subscription modules - Create a recurring product - Add a comparison price in the product's form - Have only one plan for the recurrence - Go to the product's page in eCommerce ### Current behavior before PR: If you set a comparison price for a recurring product that has only one plan it won't be shown at the product's page in eCommerce this starts happening after this commit https://github.com/odoo/enterprise/pull/53591/commits/325e9
Original PR description
### Steps to reproduce: - Install eCommerce and Subscription modules - Create a recurring product - Add a comparison price in the product's form - Have only one plan for the recurrence - Go to the product's page in eCommerce ### Current behavior before PR: If you set a comparison price for a recurring product that has only one plan it won't be shown at the product's page in eCommerce this starts happening after this commit https://github.com/odoo/enterprise/pull/53591/commits/325e9fa35486b1fa0c3622e93eef5eac54b22cf1 ### Desired behavior after PR is merged: We are now showing the striked price if we only have one plan for recurrency. opw-3990890 Forward-Port-Of: odoo/enterprise#69791 Forward-Port-Of: odoo/enterprise#69582
https://github.com/odoo/enterprise/pull/61962 introduces consistency check for the generic tax report. The check was a bit too strict (we didn't allow any mistake). This pr relaxes the constraint a bit by allowing an error as long as it's smaller than 0.1% of the base amount. task-4119817 Forward-Port-Of: odoo/enterprise#68632
Original PR description
https://github.com/odoo/enterprise/pull/61962 introduces consistency check for the generic tax report. The check was a bit too strict (we didn't allow any mistake). This pr relaxes the constraint a bit by allowing an error as long as it's smaller than 0.1% of the base amount. task-4119817 Forward-Port-Of: odoo/enterprise#68632
We overwrite the CSS of the thread popover to prevent it from being displayed in dark mode, but we missed the CSS of some elements. Task: [4111072](https://www.odoo.com/web#id=4111072&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#68445
Original PR description
We overwrite the CSS of the thread popover to prevent it from being displayed in dark mode, but we missed the CSS of some elements. Task: [4111072](https://www.odoo.com/web#id=4111072&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#68445
Since 4dfb9259762de we tokenize subscription payment when amount is sufficient, in some case that test was not true because the sum of order's recurring line was greater by an epsilon. This commit compare the two amounts relative the order's currency (rounding). opw-4176380 opw-4162841 opw-4117553 opw-4152609 Forward-Port-Of: odoo/enterprise#69808
Original PR description
Since 4dfb9259762de we tokenize subscription payment when amount is sufficient, in some case that test was not true because the sum of order's recurring line was greater by an epsilon. This commit compare the two amounts relative the order's currency (rounding). opw-4176380 opw-4162841 opw-4117553 opw-4152609 Forward-Port-Of: odoo/enterprise#69808
This reverts commit b9947b15024b8b04a87b592ca81770d5489924ea. The bugfix allows to renew an order even when the next_invoice_date != start_date for first period. The solution is to make sure the periods are correctly set at contract creation. task 4116538 Forward-Port-Of: odoo/enterprise#69825
Original PR description
This reverts commit b9947b15024b8b04a87b592ca81770d5489924ea. The bugfix allows to renew an order even when the next_invoice_date != start_date for first period. The solution is to make sure the periods are correctly set at contract creation. task 4116538 Forward-Port-Of: odoo/enterprise#69825
When there is no article to load, the form view creates a virtual record and saves it when the user closes the page or reloads it. To avoid creating empty articles, we will trigger an urgent save only if the record is dirty. Steps to reproduce the issue: 1. Delete all articles from the database 2. Open the Knowledge editor (you should see the no-content helper) 3. Reload the page (F5) => The system creates a new "Untitled" article (see the list view). TO BE: The system should not cre
Original PR description
When there is no article to load, the form view creates a virtual record and saves it when the user closes the page or reloads it. To avoid creating empty articles, we will trigger an urgent save only if the record is dirty. Steps to reproduce the issue: 1. Delete all articles from the database 2. Open the Knowledge editor (you should see the no-content helper) 3. Reload the page (F5) => The system creates a new "Untitled" article (see the list view). TO BE: The system should not create any article when reloading the view. task-4167335 Forward-Port-Of: odoo/enterprise#69560
Before this commit, assignment emails are sent when an account.move is created with a different user_id than the current one. For subscriptions it can send thousands of email depending on the database size. The user_id on the account.move is the same salesperson than the one in charge of the sale.order. It helps the consistency of communication between the customer and the company. taskid: 4096474 Forward-Port-Of: odoo/enterprise#68752
Original PR description
Before this commit, assignment emails are sent when an account.move is created with a different user_id than the current one. For subscriptions it can send thousands of email depending on the database size. The user_id on the account.move is the same salesperson than the one in charge of the sale.order. It helps the consistency of communication between the customer and the company. taskid: 4096474 Forward-Port-Of: odoo/enterprise#68752
commit [1] introduced new barcode structure. However different buisness already have printed their barcode and it could be difficult to adapt on migration. We have this issue. For the sake of the planet, we will add aliases and better alias management instead of printing in color thousands of scaleup The demo data for scale up will be removed in 19.0 [1] commit 073163f1ae3fd2c659653b773d3ed66836eb2cb2 Forward-Port-Of: odoo/enterprise#69639
Original PR description
commit [1] introduced new barcode structure. However different buisness already have printed their barcode and it could be difficult to adapt on migration. We have this issue. For the sake of the planet, we will add aliases and better alias management instead of printing in color thousands of scaleup The demo data for scale up will be removed in 19.0 [1] commit 073163f1ae3fd2c659653b773d3ed66836eb2cb2 Forward-Port-Of: odoo/enterprise#69639
When the salary configurator is in public, there is no submit button, so it raises a traceback. To avoid this we check the button exists beore disabling it Forward-Port-Of: odoo/enterprise#69821
Original PR description
When the salary configurator is in public, there is no submit button, so it raises a traceback. To avoid this we check the button exists beore disabling it Forward-Port-Of: odoo/enterprise#69821