Daily updates from Odoo
Wednesday, June 26, 2019
15 changes
Enhancements to existing features
This update adds a new Expense settings option to enable the payroll-related expense integration more easily. It also improves demo data so expense validation can be tested without extra accounting setup.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: id=1967791 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Ecommerce category links in the sitemap now match the final customer-facing URLs, including the full parent category path. This helps search engines see the same SEO-friendly category structure that shoppers use on the website.
Original PR description
Before this commit, when an user would visit a subcategory in the ecommerce, he would see a slugified URL, containing all the category hierarchy, which is good for SEO purpose. For example, if `Wheel` is a child of `Car` which is a child of `Vehicule`, then the URL would be `/shop/category/vehicule-car-wheel-3`. But on the sitemap, the parents would not be prefixed to the URL, thus the sitemap would simply show `<loc>/shop/category/wheel-3</loc>`. This commit ensure the category parents are added to the final URL of the sitemap. task-1889972
This change lets Odoo modules run specific actions immediately before and after they are upgraded. It gives teams more control over upgrade processes, helping automate preparation or follow-up tasks that previously required manual handling.
Original PR description
**Description of the issue/feature this PR addresses:** Hooks to be able to execute specific methods when upgrading a module. **Current behavior before PR:** There is no way to execute specific methods just before or after the upgrading a module. **Desired behavior after PR is merged:** New hooks: 'pre_update_hook' and 'post_update_hook' **NOTE:** I would prefer to push to previous versions, but I know your policy is to implement this kind of changes in `master` 😢 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Inventory adjustments can now start with counted quantities set to zero instead of prefilled stock values, making it easier for teams to scan and enter actual counts from scratch. Inventory lines can also be filtered or grouped by product category, helping users organize and review counts more efficiently.
Original PR description
Add an Inventory Adjustment field `prefill_counted_quantity`. True by default, when it's disabled, the inventory will generate when inventory lines with 0 as value for `product_qty` field when started. The purpose is to make simpler the use of barcode scanner to do the inventory adjustment. Task #2026952
The web interface no longer shows the “Remove” button when opening related records from list-style fields, reducing the chance that users accidentally delete or unlink a record instead of discarding changes. The button remains available in kanban-style related records where it is still needed as the only removal option.
Original PR description
When we open any x2m record (in a FormViewDialog), there is a "Remove" button to delete/unlink the opened record from parent. This button is placed besides "Discard" button and it creates little confusion in some cases. For example, in list view, there's already a bin / 'x' icon depending on the field type using which people are used to delete/unlink the record. And when they open a record, they might accidentally click "Remove" button instead of "Discard". To avoid this, now we won't show "Remove" button when we open record from x2many list view. However, we have to keep this button in case x2many of kanban as there's no other way to remove the record. task-1886913 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
Users can now enlarge small profile or related images directly from forms and cards. This makes employee and contact photos easier to view without changing page layouts, using the same zoom experience already available for eCommerce product images.
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
This update displays the company associated with records in many list views, making it easier for users working across multiple companies to see which company each item belongs to. It supports clearer day-to-day navigation and reduces confusion in multi-company setups.
Original PR description
Pad:https://pad.odoo.com/p/r.c0a23fafca9b57ddfda417f65094bb14 Task:https://www.odoo.com/web#id=1997637&action=333&active_id=1278&model=project.task&view_type=form&menu_id=4720
Employees now see how many hours they have been checked in for the current day when they are about to check out. This makes it easier to verify working time at a glance, including for employees working in time zones outside UTC.
Original PR description
Purpose ====== When an empoyee wants to check out, he does not know the number of hours he worked today. Specification ========== In the check out view, display how many hours the employee was checked in today. It should work even if the employee is in another timezone than UTC. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The project’s internal JavaScript checks now allow the latest supported language version in the master branch. This keeps development validation aligned with current platform capabilities while still catching syntax issues before they reach users.
Original PR description
ESNext is now supported in master so the max version number has been raised. Note that es-check is still used but not for the original purpose ; it is still useful for JS syntax checking.
Payroll teams can now use a dedicated wizard to index employee contracts, making contract updates easier to manage. This helps streamline payroll preparation and supports country-specific handling such as Belgian payroll requirements.
Several business list views now show the company linked to each record. This helps users working with multiple companies quickly identify which company a record belongs to and avoid confusion during daily operations.
Original PR description
Pad:https://pad.odoo.com/p/r.c0a23fafca9b57ddfda417f65094bb14 Task:https://www.odoo.com/web#id=1997637&action=333&active_id=1278&model=project.task&view_type=form&menu_id=4720
Belgian payroll users can now calculate employees' annual paid time off entitlement from validated work entries. The new workflow lets payroll teams review and adjust computed days before generating time off allocation requests, reducing manual effort and improving consistency.
Original PR description
In Belgium we need to compute the number of paid time off each employee get rights annually. New wizard to compute the number of days worked by each employee based on payslips. After computation, number of days is editable. After validation, time off allocations are generated. id=1925517
Belgian payroll support has been updated to handle PFI salary structures for retroactive payslips and to apply a missing deduction for small salary bonuses. Payroll tests were also adjusted to better cover scenarios such as employees with multiple cars, improving reliability of Belgian payroll processing.
The Sign app now guides users more directly to the document preview after sending or selecting a template, reducing unnecessary navigation. The direct signing flow is also clearer, with the recipient prefilled as the current user and updated wording for key actions.
Original PR description
-After the "Send" dialog, you have to jump on the preview, not on the signature request form unless it's a debug mode. -When "Sign Directly", prefill the "Sent To" field in the dialog by the current user/ -When clicking on a card from templates (and not on a button of this card), it should go to the preview(edition of fields) of the document. -Moved Document notebook in technical features. -Renamed "Edit" into "Properties" Task Link: https://www.odoo.com/web?#id=1935510&action=327&model=project.task&view_type=form&menu_id=4720 Pad Link: https://pad.odoo.com/p/r.8980774e94f2788de982538aa0fa00d6
Payroll setup data is adjusted so the default “Employee” structure type is only included with demo data rather than every installation. Employee contracts now choose working schedules from the structure type when available, otherwise falling back to the company default, helping keep real payroll setups cleaner and more consistent.
Original PR description
Move "Employee" structure type from data to demo data. In contract, by default, select resource calendar from structure type. If there aren't structure type, select default company resource calendar id=1959259