Thursday, January 2, 2025
10 changes
5 changes
Enhancements to existing features
Removed an unused piece of WhatsApp messaging code that was left over after a related interface change. This has no expected change for users, but keeps the codebase simpler and easier to maintain.
Original PR description
Since odoo/odoo#186084, the `hasSendButtonNonEditing` getter has been removed from the composer template. This commit removes that getter, as it's now dead code. Related to odoo/odoo#192103
Cohort reports can now be viewed using quarterly periods, giving teams a broader time-based perspective alongside existing options. This helps business users spot longer-term trends more easily when analyzing customer or activity cohorts.
Original PR description
Adds the ability to see cohort on a quarterly basis.
Restaurant teams can now update the table booking appointment type even while a point-of-sale session is open. After reloading, the POS resynchronizes with the updated setting, giving staff more flexibility without needing to close active sessions.
Original PR description
Previously, the setting "Table booking: appointment type" could not be modified while a session was open. With this commit, this setting can now be modified, and the POS will resynchronize after reloading Requires Community PR https://github.com/odoo/odoo/pull/191396 task-4380609
The contract signing setup wizard now offers an Upload PDF button when no signing templates are available. This makes it easier for HR users to continue preparing contract signature requests without first creating or finding an existing template.
Original PR description
This PR improves the configuration of the sign request template by adding an `Upload PDF` button in the wizard when no templates are available. task-4243509
The Field Service Tasks Analysis report was adjusted to match recent changes that removed an inactive-task filter. This keeps reporting views working correctly without requiring broader changes to field service or task analysis reports.
Original PR description
- Removed the inactive filter in the Tasks Analysis report, so we need to update the xpath accordingly. Technical: - If the `inactive` filter is added in the `project_task_view_search_fsm_base` view, it will require the removal of both the Task Analysis report and the FSM report. Hence, we should not include the `inactive` filter in the `project_task_view_search_fsm_base`. Related : https://github.com/odoo/odoo/pull/175518 task-4037091
4 changes
Enhancements to existing features
This change improves how Odoo counts expenses linked to a sales order by making the lookup more efficient. Users should see faster loading of the related expenses smart button on sales order forms, especially where many expenses exist.
Original PR description
## Description `sale.order._compute_expense_count` does a `_read_group` with a domain only based on `sale_order_id`, which is an unindexed FKey, leading to a guaranteed `Seq.Scan`. This `_compute_expense_count` is used to compute the count of related expenses for a `sale.order`, shown as a smart button on the form view, which is a frequent operation. ## Reference task-3977983 --- 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 clarifies the comparison filter in the accounting reports by dynamically displaying the number of periods being compared. Previously, the label was confusing, especially when comparing to multiple periods. This change ensures users understand the scope of their analysis.
Original PR description
Before this commit, the button label displayed as 'Comparison: <previous_period>' (where 'previous_period' was the period preceding the compared period), regardless of the comparison type selected.…
This update cleans up and reorganizes Argentina withholding and perception tax records so they are easier to use and better aligned with current tax terminology. It also removes outdated duplicate taxes, corrects tax grouping, and relaxes a form requirement when a tax is not an Argentina withholding tax.
Original PR description
_l10n_ar_withholding_: 1) Make not required "WTH Tax" (l10n_ar_tax_type) field in account.tax form view if "Argentina Tax Type" (l10n_ar_type_tax_use) is 'customer' or 'supplier'. So, if the tax is…
_l10n_ar_withholding_: 1) Make not required "WTH Tax" (l10n_ar_tax_type) field in account.tax form view if "Argentina Tax Type" (l10n_ar_type_tax_use) is 'customer' or 'supplier'. So, if the tax is not for argentina withholding then the "WTH Tax" field will not be required. 2) "Earnings WTH A" tax is deleted because is not used any more. 3) Earnings WTH taxes have "VAT 21%" as "Tax Group", in this pr is changed to "Withholding" tax group. 4) Change IIBB Withholding and Earnings 'name' and 'description' fields on account.tax model. Delete words "incurred" or "applied", change word 'earnings' to 'profits'. Also adapt translations. WTH SUSS and WTH Earnings taxes are duplicated, delete both taxes from addons/l10n_ar_withholding/data/template/account.tax-ar_ri.csv. IIBB withholdings and perception state names abreviations are changed, for example: old name --> IIBB WTH Chubut I, new name --> IIBB WTH CHT 0%. 5) Update addons/l10n_ar_withholding/data/template/account.tax-ar_ex.csv external ids with new state name abreviations and also profits withholding taxes (example: old id --> ex_tax_withholding_profits_regimen_31_insc, new id: ex_tax_withholding_profits_regimen_31_insc). 6) Change 'amount_type' from 'fixed' to 'percent' on taxes on addons/l10n_ar/data/template/account.tax-ar_ex.csv 7) Create file addons/l10n_ar_withholding/data/template/account.tax-ar_base.csv with iibb withholding iibb incurred taxes and delete those taxes from addons/l10n_ar_withholding/data/template/account.tax-ar_ri.csv 8) Add on file addons/l10n_ar_withholding/data/template/account.tax-ar_ex.csv iibb withholding applied taxes and profits withholding applied taxes . Delete those taxes from addons/l10n_ar_withholding/data/template/account.tax-ar_ri.csv . 9) Rename tax group file from addons/l10n_ar_withholding/data/template/account.tax.group-ar_ri.csv to addons/l10n_ar_withholding/data/template/account.tax.group-ar_base.csv 10) Adapt addons/l10n_ar_withholding/demo/account_demo.py and addons/l10n_ar_withholding/tests/test_withholding_ar_ri.py with the new external ids. _l10n_ar_: Change perception 'name', 'description' and 'invoice_label' fields on account.tax model. On field 'name' set the same state abbreviation as abbreviations applied on withholding ar taxes. On the field 'description' delete the word "applied or incurred". On field 'invoice_label' delete the last letter (I or A). Also translations are adapted. _**Task Adhoc side**_: 43411 _**Task Latam side**_: 1289 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves performance in the Expenses app by making expense lines easier for the system to find by their related expense sheet. Users may notice faster loading or processing in areas that read, submit, or recalculate expense sheet information, especially as data volume grows.
Original PR description
## Why
- Inverse of the One2many `expense_line_ids`, the ORM will search on it to resolve the read on the field
- Used as a traversable dependency of a few compute methods (`@api. depends('sheet_id.xxx')`), index will be hit when ORM resolves the computation of dependencies to know what compute method to call when the dependency changed.
- Frequently used as the traversal field of related fields, index will be hit when reading on the field in SQL in `_traverse_related_sql`.
- Using Full index, as there aren't many `NULL`/`False` entries, as it's moslty pending expense lines that are pending for reporting. So a search on the NULL criteria (done in `get_expenses_to_submit`) will hit the index.
## Reference
task-3977983
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update changes the security support documentation to show that Odoo 15.0 is no longer actively supported. It helps customers and partners plan upgrades and understand which versions remain covered for security maintenance.
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
Before this commit, the button label displayed as 'Comparison: <previous_period>' (where 'previous_period' was the period preceding the compared period), regardless of the comparison type selected. For example, if comparing October 2024 to previous months, the label would appear as 'Comparison: Sep 2024'. This caused confusion for users when comparing a period to multiple previous ones, as only the last period was displayed in the label. After this commit, the button label is now dynamic and reflects the selected comparison: - When comparing to previous periods: 'Comparison: <periods_number> Previous Periods' - When comparing to the previous period: 'Comparison: Previous Period' - When comparing to the same period in previous years: 'Comparison: <periods_number> Previous Years' - When comparing to the same period in the previous year: 'Comparison: Previous Pear' - When we don't compare to another period/year: 'Comparison' Here, 'periods_number' refers to the number of periods or years being compared. task-id: 4267209 Forward-Port-Of: odoo/enterprise#73944