Daily updates from Odoo
Monday, May 6, 2024
19 changes · master
Enhancements to existing features
WhatsApp configuration options are now shown under Discuss settings instead of Email settings. This makes the settings page clearer and helps users find WhatsApp-related options in the expected place.
Original PR description
### whatsapp Following the addition of the Email settings group, moves whatsapp settings to the Discuss settings group. task-3859594
Account reports now keep their fixed top-level sections in their original order when users sort report lines. This preserves the intended structure of official reports while still sorting the detailed content within each section.
Original PR description
For most reports (especially the official ones) it is not relevant to sort the fixed parts. That's why this commit excludes the hierarchy level 0 lines from sorting. This makes it so the structure of the report is preserved while sorting, but the content of each part does get sorted. task: 3645935
Invoice and subscription screens were simplified by moving rarely used Intrastat and subscription fields into debug mode, especially on mobile. Column widths were also adjusted to reduce empty space, making invoicing views easier to read and navigate.
Original PR description
*: account_accountant, account_intrastat, sale_subscription This commit aims at improving readability by moving some less used fields to the debug mode Community PR: https://github.com/odoo/odoo/pull/163014 task-3642419
The French FEC import now lets users add a prefix to imported journal entry names and decide whether matching records should be ignored or updated. This helps avoid clashes when importing accounting files by fiscal year, especially when entries in different years share the same name.
Original PR description
In order to handle clashes between imported records and DB records, the following import improvements were incorporated: 1. Added the option to accept a prefix added to moves names. 2. Added the option to give the user control over what should happen to such clashes (ignore or update). User import SAF-T/FEC by fiscal year for simplicity and also because too big file generate time out. We import and update the records by name, but records having the same name in different fiscal years cause import data clashing. Users should be able to differentiate between records imported in different fiscal years. task-3830049
The Knowledge welcome template now encourages users to try the checklist feature sooner by placing the checkbox example first. Wide tables inserted from the editor now automatically use the full article width on desktop, making larger tables easier to read.
Original PR description
### knowledge reorder checkbox elements in example welcome template This puts the checkbox element "Check to mark as done." first in the example list. This calls the user to early action on their part (to try it out for themselves). increase article width on insertion of a large table On computers (or any device capable of seeing the TablePicker), tables inserted with the /table command now trigger full article width if they have at least 5 columns. Note that this cannot happen with tables inserted on mobile devices, as they have a standard fixed size of 3x3. Existing tables onto which more columns are added will not modify article width. Tables with a lot of columns are hard to read with the default article width, and they did not previously increase that width on insertion. task-3847398
Helpdesk managers can now access canned responses directly from the Helpdesk app, even when live chat is not enabled for a team. This makes reusable support replies easier to manage and removes unnecessary options from the helpdesk team form.
Original PR description
We made the following changes: ------------ - Remove some elements and strings from the helpdesk team form the view - Currently, the canned responses menu can be accessed by the helpdesk manager only if livechat is activated in the helpdesk team. In this commit, we have moved it to the helpdesk, so it can be accessed without live chat. task-3776070
Users can now configure custom appointment availability in a simple pop-up without leaving the calendar. This keeps the sharing flow smoother, saves updates before copying the link, and helps ensure invite links point to the correct selected users.
Original PR description
In order to ease the use of custom appointment types, the user, after selecting custom slots in the calendar view, can go to "Configure" button. This creates the appointment type, and before this commit, it redirects to the form view. In order to stay on this view and keep the flow simple and smooth, the button now opens a custom dialog form view, simplified and with custom buttons: "Copy Link" (also saving and closing the dialog) and "More options" leading to the full form view, as it was working before. The user can change the created appointment type and when leaving through one of those two buttons, the appointment is saved and the invitation is updated if users were updated. This ensures that the link is correctly leading to selected users. Task-3805720
Subscription order history has been reorganized so key events such as cancellations, currency changes, and pricing updates are recorded more clearly and in the right order. This gives sales and subscription teams a more reliable view of customer subscription changes while reducing incorrect or confusing log entries.
Sales teams can now more easily filter and group commission and subscription reports using useful criteria such as referrers and subscription log details. This makes it faster to analyze sales activity and understand performance drivers without manual workarounds.
Original PR description
Before this PR, some useful filters and group by were missing.
Resolved issues and error corrections
This fixes an internal test setup issue in the Dutch SBR reporting module caused by an incorrect code rebase. It helps keep automated checks reliable, reducing the risk of unnoticed problems in Dutch tax reporting functionality.
Original PR description
A bad rebase removed the classmethod attribute on the setUpClass runbot-64610
A payroll account test sequence was corrected so the automated checks follow the intended order. This helps keep Belgian payroll account testing reliable and reduces the risk of false test failures during future updates.
Original PR description
This commit fixes wrongly swapped test steps in hr_contract_salary_tour_2
The task portal now uses the correct timesheet hours value when showing subtask totals. This prevents missing or incorrectly formatted hour values for customers viewing project task information online.
Original PR description
Before this commit, due to a bad rebase, the changes made in odoo/odoo#122814 changed `task.subtask_effective_hours` by `timesheets_by_subtask_amount` in span elements inside `hr_timesheet.portal_timesheet_table` but the variable `timesheets_by_subtask_amount` does not exist inside that template. That's why the value cannot be converted by the widget defined for that span element. This commit adapts the template to be sure `task.subtask_effective_hours` is used instead of that variable. runbot-64479
Miscellaneous changes
The reconciliation of journal items imported from Winbooks is done when all those items are posted. However if one of the imported items to reconcile have zero as balance, it will trigger an error "You are trying to reconcile some entries that are already reconciled." because Odoo consider zero balance lines as reconciled and block the user of posting the entries. This fix removes the reconciliation data when the Winbooks file is imported if the item has a zero balance since this item does no
Original PR description
The reconciliation of journal items imported from Winbooks is done when all those items are posted. However if one of the imported items to reconcile have zero as balance, it will trigger an error "You are trying to reconcile some entries that are already reconciled." because Odoo consider zero balance lines as reconciled and block the user of posting the entries. This fix removes the reconciliation data when the Winbooks file is imported if the item has a zero balance since this item does not need to be reconciled in the future. opw-3830355 Forward-Port-Of: odoo/enterprise#61743
*: product, stock_barcode product: - Add a on change method on barcode to add autofill record. - Find products in barcodelookup.com from the barcode field stock_barcode: - Display a popup(form-view) to create a product if the scanned product is not available in the database and autofill the record. Co-authored-by: jva-odoo jva@odoo.com Co-authored-by: rare-odoo rare@odoo.com task-3871453 Forward-Port-Of: odoo/enterprise#61949
Original PR description
*: product, stock_barcode product: - Add a on change method on barcode to add autofill record. - Find products in barcodelookup.com from the barcode field stock_barcode: - Display a popup(form-view) to create a product if the scanned product is not available in the database and autofill the record. Co-authored-by: jva-odoo jva@odoo.com Co-authored-by: rare-odoo rare@odoo.com task-3871453 Forward-Port-Of: odoo/enterprise#61949
With [1], we have changed the field name ``l10n_in_gstr_gst_production_env`` to ``l10n_in_edi_production_env``in some files, but its reference was still present at [2]. This causes an exception when the users follow below steps: Step to reproduce: - Install ``l10n_in_reports_gstr`` module - Switch to ``IN Company`` - Accounting > Configuration > Indian Integration > Indian GST - Click on ``Buy Credits`` Traceback: ``AttributeError: 'res.config.settings' object has no attribute
Original PR description
With [1], we have changed the field name ``l10n_in_gstr_gst_production_env`` to ``l10n_in_edi_production_env``in some files, but its reference was still present at [2]. This causes an exception when the users follow below steps: Step to reproduce: - Install ``l10n_in_reports_gstr`` module - Switch to ``IN Company`` - Accounting > Configuration > Indian Integration > Indian GST - Click on ``Buy Credits`` Traceback: ``AttributeError: 'res.config.settings' object has no attribute 'l10n_in_gstr_gst_production_env'`` This commit will resolve the above error by changing the name of the field to ``l10n_in_edi_production_env`` at [2]. [1] : https://github.com/odoo/enterprise/commit/328c01e601d7905df3ebfb4c6b014c7dbf09fce2 [2] : https://github.com/odoo/enterprise/blob/ba99dd4c236353c43376210a9aabcb0af5bd0299/l10n_in_reports_gstr/models/res_config_settings.py#L68C9-L69C88 sentry-5287121031 Forward-Port-Of: odoo/enterprise#61829
…igher rules Have rules such as: 1. no domain, notification order: 1 2. no domain, notification order: 2 3. a domain that doesn't match the record, notification order: 2 Manually validate the rule 1, that is, do not hit the button of the action, rather, enter the popup of the approvals, and validate the rule. The spec of the flow is that, when all rules from a level (or notification order) have been validated, rules that have a higher order will trigger an activity and a notification
Original PR description
…igher rules Have rules such as: 1. no domain, notification order: 1 2. no domain, notification order: 2 3. a domain that doesn't match the record, notification order: 2 Manually validate the rule 1, that is, do not hit the button of the action, rather, enter the popup of the approvals, and validate the rule. The spec of the flow is that, when all rules from a level (or notification order) have been validated, rules that have a higher order will trigger an activity and a notification to their responsible. After all, those rules are "next in line". Before this commit, both rule 2 and 3 sent a notification and created an activity for the current record. This was wrong as rule 3 should not be considered, because its domain doesn't match the record. After this commit, only rule 2 sends a notification and creates an activity. opw-3815732 Forward-Port-Of: odoo/enterprise#61746
Added a test for partners vat export in DateV report. task-3866785 Forward-Port-Of: odoo/enterprise#61202
Original PR description
Added a test for partners vat export in DateV report. task-3866785 Forward-Port-Of: odoo/enterprise#61202
The query defined `_l10n_pe_get_txt_11_data` does not define an order. It can result in an undeterministic order. We define it based on the date then id. Linked to runbot error 63997 Forward-Port-Of: odoo/enterprise#61867
Original PR description
The query defined `_l10n_pe_get_txt_11_data` does not define an order. It can result in an undeterministic order. We define it based on the date then id. Linked to runbot error 63997 Forward-Port-Of: odoo/enterprise#61867
This will fix the computation of the double holiday pay recovery to match legal requirements. Task: 3893867 Forward-Port-Of: odoo/enterprise#61540
Original PR description
This will fix the computation of the double holiday pay recovery to match legal requirements. Task: 3893867 Forward-Port-Of: odoo/enterprise#61540