Daily updates from Odoo
Friday, November 22, 2024
18 changes
8 changes
Enhancements to existing features
Bulk changes to helpdesk tickets and field service tasks now reuse sales order line lookups instead of repeating the same search for each record. This reduces processing time and database load when many records share the same customer or team, making large updates noticeably faster.
Original PR description
Steps to reproduce: ------------------- 1. Install Project, Timesheets, Helpdesk and Sales apps 2. Create many tickets (e.g. 5k) associated with the same helpdesk team 3. Change the project linked to…
Steps to reproduce:
-------------------
1. Install Project, Timesheets, Helpdesk and Sales apps
2. Create many tickets (e.g. 5k) associated with the same helpdesk team
3. Change the project linked to the helpdesk team
4. It should update the SOL of all tickets linked to that team
Other way to reproduce:
1. Install Project, Timesheets, Helpdesk and Sales apps
2. Create many tickets
3. Go to the list view of tickets
4. Update the customer in all those tickets
Fix:
-------------------
The idea is to batch the RPC (search) made by the method "_get_last_sol_of_customer()". Avoiding to do an RPC for each ticket, we can now re-use the computed SOLs as we store them in a dictionary. It particularly improve performance if we compute the sale_line_id of many tickets having similar commercial partners.
Benchmark:
-------------------
- Usecase: Create 5k tickets associated with an helpdesk team, change the project linked to the helpdesk team, it should update the SOL of all those tickets.
- Parameters: In local, run with "--limit-memory-soft=8589934592", "--limit-memory-hard=8589934592".
- Results:
Without optimization: 34 seconds, 30 665 queries
With optimization: 22 seconds, 15 397 queries
related-https://github.com/odoo/odoo/pull/185132
task-4255293Referral rewards are easier to browse and manage: reward cards now show the award image, the reward list includes the Gift Responsible, and the buying message is clearer. These updates help HR teams and employees better understand reward options and ownership at a glance.
Original PR description
1. Show the image of the award in kanban view. 2. Add `Gift Responsible` to reward list view. 3. Update the reward buying message. task-4296804
Users can now duplicate approval requests directly from the form and list view menu. This makes it faster to create similar requests and reduces repetitive manual entry.
Original PR description
This PR improves the approval request form and list view by adding a `Duplicate` option to the menu. task-3685226
Lithuanian payroll rules now calculate taxable and sick-pay amounts directly inside the relevant salary rules instead of relying on a hidden payslip method. This makes payroll calculations easier to review, maintain, and validate without changing the intended business outcome.
Original PR description
Problem ---------- The method "payslip._get_l10n_lt_taxable_amount" is used in salary rules that makes the computation non-transparent. Objective ---------- Put this method in the python code field of salary rules directly Solution ---------- Done, with the sick argument removed. task-4134314
Helpdesk tickets submitted through the website no longer show the automatic “external submission” text as if it were a message from a private user. The information is still kept as an internal note and in the ticket description, reducing confusion for support teams.
Original PR description
[IMP] website_helpdesk: remove 'external submission' from messages Before this commit: - When submitting a ticket through the web form, 'external submission' is displayed as a message from 'private user' and as a note. But, the private user haven't really send any message. After this commit: - Keep the information only as a note and in the description. task-4216270
Web Studio's automated tests were updated to use a newer testing approach, replacing older test utilities. This is an internal quality improvement that helps maintain reliability without changing day-to-day user features.
Original PR description
This commit aims to convert QUnit tests to hoot that rely on legacy mail tests utils and legacy bus tests utils. Part of task-3818666
Users can now create and edit Brazil Avatax operation types in Odoo, matching custom setup options available in the Avatax portal. This helps businesses keep their Odoo tax configuration aligned with customer-specific Avatax settings.
Original PR description
We include the default ones Avatax has in their portal. But customers can create custom operation types on the Avatax side and so need to do similar on our side as well. task-4288101
Studio now includes an Actions tab where users can quickly view and create automated server actions for a model. Newly created actions are automatically added to the model's contextual menu, making common workflow automation easier to set up and use.
Original PR description
This commit adds a studio Tab to quickly access and create ir.actions.server objects. Upon creation, created actions are automatically added to the model's contextual menu. task-4268990
6 changes
Enhancements to existing features
Cashiers can now search for products in Point of Sale using their barcode, instead of only relying on product names or other details. This makes checkout faster and reduces confusion when barcode-based searches previously returned no results.
Original PR description
Before this commit, searching with the barcode of a product would not show any results. opw-4330143 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Default values for company-specific fields will now be chosen consistently, instead of varying based on the individual user who triggered them. This reduces unexpected behavior across companies and can improve performance by reusing cached defaults more effectively.
Original PR description
when an ir.default record with user_id is created, the result will be used as the fallback value for undefined company-dependent column value. It will cause user-dependent fallback which is logically wrong. This commit forces the fallback value to be fetched with SUPERUSER to make fallback always not user-dependent and increase the cache hit rate for _get_model_defaults 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
Restaurant point-of-sale orders now remain linked to their original table when tables are merged and later separated. This prevents lost or misplaced orders, making table management more reliable for restaurant staff.
Original PR description
Before this commit: =================== When merging tables, the order from the original table was transferred to the destination table, and the original table's order was deleted. As a result, when tables were unmerged, the original table's order could not be restored. After this commit: ================== When tables are merged and later unmerged, the original table's orders are successfully restored. This ensures that each table retains its initial order even after being merged and unmerged. Task- 4224207
The chart configuration panel now uses clearer wording for stacked line and bar chart options, changing labels such as “stacked linechart” to “stacked line chart.” The line chart panel spacing was also tightened so related options appear more consistently, making chart setup easier to understand.
Original PR description
Change the checkbox label of stacked charts from `stacked linechart` to `stacked line chart` in the chart configuration panel. Same for bar charts. Also removed padding between `stacked` and `cumulative` checkboxes in the line chart panel. Task: [4290275](https://www.odoo.com/web#id=4290275&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
Kitchen preparation cards now show all table numbers involved when restaurant tables are merged, instead of only the destination table. This helps kitchen staff identify orders more clearly and reduces confusion during service.
Original PR description
Before this commit: ================ When tables were merged in the restaurant, the kitchen display only showed the destination table number on the preparation card. After this commit: ================== Now, if tables are merged (e.g., Table 1 & Table 2), the kitchen display will show both table numbers (e.g., 1&2) on the preparation card. This provides better clarity for the kitchen staff by reflecting the merged table arrangement Task- 4224207 Related Community PR: https://github.com/odoo/odoo/pull/183070
Financial report actions that require the main company and all branches are now clickable and show a clear message when the right company selection is missing. This helps users understand what to do instead of assuming a disabled button is a system issue, reducing confusion and support requests.
Original PR description
When you have a company with branches in a database, some reports only make sense when you have the main company with all its branches selected. Currently some report actions (buttons) were disabled if you didn't have your main company and its branches selected, without any information on why the buttons were disabled. This resulted in people creating tickets because they thought something was wrong. This change makes the buttons clickable again, but instead displays a message saying that the user should select the main company and its branches in order to save a sensible report. [task-4260501](https://www.odoo.com/odoo/all-tasks/4260501)
4 changes
Enhancements to existing features
This update provides Romania with the option to generate a 4 or 5-column trial balance report, aligning with their local accounting standards. The underlying trial balance implementation has been improved for easier customization and future updates. This ensures accurate reporting for Romanian businesses using Odoo Enterprise.
Original PR description
Romania does not use the 3-column trial balance report, instead they use a 4-column and 5-column variant. This commit adds the 4/5-column report as variants to the standard trial balance. The standard trial balance implementation has been changed to be easier to override and add column groups. task: 3810685
This update adds a new XML export button to the German Intrastat report. This allows businesses to easily generate the required XML files for submitting their Intrastat reports to German authorities, streamlining the reporting process and ensuring compliance. The change is part of ongoing improvements to our German localization features.
Original PR description
This commit add the export to xml button on the intrastat report for Germany. More information can be found here: - https://erhebungsportal.estatistik.de/Erhebungsportal/informationen/hilfe-zur-meldungsabgabe-3749 task-4194404 Forward-Port-Of: odoo/enterprise#71785
This update introduces a new system parameter in the accounting settings, allowing users to specify a custom VAT number instead of the default accounting firm's VAT for CodaBox connections. This flexibility addresses situations where accounting firms require a different VAT to be used as their contract number, improving the connection's accuracy and usability.
Original PR description
Currently, the accounting firm's VAT is used for the CodaBox connection but sometimes, accounting firms need to use a different VAT as their contract number. This adds a system parameter that if filled, is used instead of the firm's VAT. task-4335294
This update ensures that the names of invoice reports generated by the l10n_mx_edi module now align with the corresponding XML invoice data. This improves data consistency and simplifies reporting processes for Mexican businesses using Odoo Enterprise. It addresses a user request for a more straightforward reporting experience.
Original PR description
Users require the name of the invoice report to be the same as the xml. task-4284482