Daily updates from Odoo
Tuesday, July 1, 2025
14 changes · master
Enhancements to existing features
The accounting report test suite was adjusted to match the standard payment and receipt accounts now created automatically with the chart of accounts. This prevents internal test conflicts and helps keep accounting-related updates reliable without changing day-to-day user workflows.
Original PR description
In this PR: - As part of recent changes, the default Outstanding Payment/Receipts accounts are now always created when the Chart of Accounts is loaded, and several test cases were updated to avoid unique constraint errors. - Previously, these test cases manually created accounts with codes like `OSTR00` and `OSTP00`. Now that these accounts are created by default, attempts to redefine them or change their codes have led to conflicts. - This commit updates the affected test cases to: - Use the correct default account codes directly (101403, 101404) - Avoid reassignment of codes that are now created by the CoA template task-4826385 Forward-Port-Of: odoo/enterprise#88802 Forward-Port-Of: odoo/enterprise#88068
Salary offers can now include a contract end date. When an offer is accepted and the employee contract is created, that end date is automatically applied, reducing manual follow-up and improving contract accuracy.
Original PR description
this commit added contract end date in offer, If the offer contract end date is set, then the created contract will have the end date field populated task- 4853216
Duplicating a salary attachment no longer carries over the amount already paid. This prevents copied records from inheriting case-specific payment history, helping payroll teams start each duplicate with accurate values.
Original PR description
Task: 4825871
This update replaces an outdated stock picking date with the record creation date in related delivery, subscription, and reporting logic. It improves the reliability of stock picking filters and reports, with upgrade support handled separately.
Original PR description
This change was suggested by a contributor, but it requires an upgrade script, so a set of 3 new PRs was created. The original purpose was to improve the stock picking filtering in `simulate_period` test helper method. While working on this, it became apparent that the `date` field in stock picking is useless and it should be replaced by `create_date`. Related: https://github.com/odoo/odoo/pull/213949 https://github.com/odoo/enterprise/pull/87494 https://github.com/odoo/upgrade/pull/7852 Original community PRs: https://github.com/odoo/odoo/pull/171895 https://github.com/odoo/enterprise/pull/66084
Payroll payment reports now use the clearer label “payment date,” and payslips are automatically updated with that date. US payslip layouts are simplified to show the payment date, hide less relevant employee details, and display only the last four digits of bank accounts for clearer employee communication.
Original PR description
When creating a payment report, the user must can choose the effective date. The term is ambiguous and is replaced by this commit by payment date. Additonnaly, the pay_date field on the payslip is automatically filled according to the payment date of the attached payment report. Also, this PR improves the US payslip template to better follow best practices: - The payment date is added - The job position, department and worked days are hidden - The phrasing of the bottom sentence has been changed and only the last four digits of the bank account are shown task-4814800
Timesheet entries now rely directly on their linked project to determine timesheet behavior, instead of using a separate internal marker. This reduces duplicated logic and helps keep timesheet reporting, merging, and timer workflows more consistent.
Original PR description
- Previously, the `is_timesheet` field was set based on the project associated with the timesheet. In this commit, we removed the `is_timesheet` field and now manage the logic through `project_id`. task-4759383
The appraisal templates were updated with clearer, corrected wording based on feedback. This helps managers and employees see more accurate appraisal text, reducing confusion from awkward or incorrect phrasing.
Original PR description
Edited the template wording to fix some incorrect translations task: 4791321
Several website-related apps now use a newer, more consistent way to define filtering rules. This improves maintainability and helps keep behavior consistent across appointments, helpdesk, knowledge, live chat, sales, stock, and related website features.
Original PR description
odoo/odoo#206891
This update modernizes how inventory-related features define search filters across manufacturing, quality, barcode, accounting, rentals, and localization flows. It should make these areas easier to maintain and reduce the risk of inconsistent filtering behavior without changing day-to-day workflows.
Original PR description
task-4280707 odoo/odoo#216505
Australian payroll rule parameters have been updated for the 2025 period. This helps ensure payroll calculations use the latest applicable values, supporting accurate payslips and compliance for Australian employees.
Original PR description
Forward-Port-Of: odoo/enterprise#88323
This update aligns enterprise online store components with recent community platform changes. It helps keep the eCommerce experience consistent and maintainable after upstream updates, with no major business process change expected.
Original PR description
Backport of 24e39d1a6169a36076e9dfcfba2200db8ab8748a (post-freeze) task-4485463 Forward-Port-Of: odoo/enterprise#88920
Appointment sharing links are now generated in one consistent place, reducing duplicate behavior across calendar, form, Kanban, and Gantt flows. Users get cleaner name-based links when possible, fewer duplicate invites, and more reliable link editing and creation.
Original PR description
Purpose: The short_code generation mechanism is made central, such that Kanban, Form, and Gantt views' share invite's code duplication can be avoided. Specifications: 1. Generate a unique link. Case…
Purpose: The short_code generation mechanism is made central, such that Kanban, Form, and Gantt views' share invite's code duplication can be avoided. Specifications: 1. Generate a unique link. Case 1: Generate name based link when no link exists for the appointment eg. /schedule-a-demo. Case 2: If a link exists for the appointment: Retrieve the existing link for the current configuration, or else generate a random code. 2. Avoid invite duplication on appointment duplication. 3. Change the button string from Cancel to Discard and short_code_unique_warning in view appointment_invite_view_form. 4. Remove AppointmentInviteViewFormController and associated files, as the same code is done on the server side to avoid code duplication. 5. Generate an appointment name-based link(if the link does not exist)for the appointment listed in the dropdown on the calendar side. 6. We can now alter the short_code of existing link and generate a new link. 7. Set default appointment type when we click on New btn in list view of links of the appointment. 8. Update the appointment name which is created via 'Share Calendar' click. 9. Test case has been created so above functional flow doesn't break. Task-4610207 Co-authored-by: Aurélien awa@odoo.com
Belgian payroll now places the ONSS CO2 fee before the employer ONSS contribution and includes it in that employer contribution total. This helps ensure payslip calculations and reporting better reflect the required treatment of company car CO2 fees.
Original PR description
The ONSS CO2 Fee must appear before the ONSS employer rule and included in its sum. task-3506696
The Partner Ledger no longer shows debit and credit amounts on initial balance and total lines. This reduces confusion from large historical amounts that do not relate directly to the selected reporting period.
Original PR description
Users are sometimes confused because Debit and Credit can show quite high amounts not related to the present period because of the initial balance. We hide these columns for the initial balances, and to remain consistent, for the totals as well in the partner ledger. taskid: 4261294