Daily updates from Odoo
Monday, August 5, 2019
16 changes
Enhancements to existing features
Odoo now checks required Python packages by their installable package names and supported versions, rather than only testing whether they can be imported. This makes dependency messages clearer for administrators and helps avoid setup issues when modules require specific package versions.
Original PR description
Use [pkg_resources.get_distribution()](https://setuptools.readthedocs.io/en/latest/pkg_resources.html#getting-or-creating-distributions) to check if python external
dependencies are installed, instead of trying an import.
This better expresses which python distribution needs to be installed
and allows declaring a minimum supported version such as.
```python
'external_dependencies': {
'python': [
'pyserial>=3'
]
}
```
Close #25541
[updated to show an example]
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update adds a dedicated tax group widget on invoices and journal entries, making it easier to adjust grouped tax amounts when rounding is needed. It helps accounting users manage tax totals more accurately directly from the document screen.
Original PR description
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Attachments will now use the latest related record name instead of relying on a saved copy that can become outdated. This keeps displayed attachment information more accurate when records are renamed, with minimal impact on day-to-day use.
Original PR description
This commit removes the store property of `res_name` from `ir.attachment` as it doesn't need to be stored and could contain outdated information. Task: #1943295 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves error messages when incorrect dependencies cause failures during migrations or development. It helps teams identify the source of dependency problems faster, reducing debugging time and support effort.
Original PR description
During a migration process or developpment if a deps is wrong, it is hard to find where is issue come. same as https://github.com/odoo/odoo/pull/31889 @odony @nim-odoo -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The CRM reporting filter previously labeled “Contents” is now labeled “Activity Description.” This makes it easier for users to understand that the filter searches activity descriptions, improving usability without changing behavior.
Original PR description
task: https://www.odoo.com/web?#id=2008515&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 pad: https://pad.odoo.com/p/r.28b0be0a1a502fa9068127d03b2d7431 Before this commit, at custom filter 'Contents' option is there for filtering by activity description. For more usability only rename is needed. By this commit 'contents' is changed to 'Activity Description'. User can filter records by activity description.
The Mexican electronic invoicing module now checks for external Python dependencies using the official distribution names from PyPI. This improves installation and validation reliability without changing day-to-day user workflows.
Original PR description
To go with https://github.com/odoo/odoo/pull/25549
This change removes a misleading legacy setting that could make database upgrades incomplete or unreliable. It affects many business apps and helps ensure future upgrades handle renamed fields through safer, more complete migration processes.
Original PR description
This attribute is misleading as it is insufficient to correctly upgrade the database. It only renames the column in the database, but other operations are needed, like updating the corresponding `ir.model.fields` record (and its xmlid). The default values and the translations are also lost during the upgrade. Moreover, this feature was misused. It was: - left on fields during multiple versions. - used on reports (SQL views). This would be ok if the feature was complete, but, as is, it was useless. - kept unchanged after a second renaming of the field (which can happen versions later the first rename). - used, even when the meaning of the field changed. i.e. the field `archived` has been renamed to the classic `active`, but the value in the database should be switched.
Customers can now preview and sign field service worksheets from the portal, while emailed worksheet reports have a clearer layout and better content. The update also streamlines material handling by using sales order lines directly, improving pricing, discounts, quantities, and consistency with sales documents.
Original PR description
This merge improves the worksheet flow and design. It provides: - a portal interface: the customer can see its worksheet from its tasks on the portal - refresh the worksheet report to be clearer - improve the flow of report sending to the final customer - display, on the portal preview, the information of material products. As we need the same informations as if the material was added on the sales order, we remove the product map and directly use the sales lines. See sub commits for more details. Task-2009558
Mexican electronic invoicing features that were previously split across separate add-ons are now included in the main Mexican EDI module. This simplifies setup and ensures cancellation, payment, customs, external trade, and cash-basis tax processes work together more consistently with Mexican SAT requirements.
Original PR description
Because a lot of modules were added in stable in order to add features/fixes, it is an opportunity to merge the modules in master.
Document managers can now give selected groups read-only access to folders and limit folder contents so users only see documents owned by them. Shared document access is also checked against the share creator's current permissions, making access behavior more consistent and controlled.
Original PR description
This commit allows documents managers to add readonly groups to folders and to restrict the content by document owner. adds two new fields (`read_group_ids` and `user_specific`) to `documents.folder`. Task: #1915003
Online appointments now open by default in a kanban-style view, making scheduled events easier to scan and access. The list view also shows appointment locations and displays assigned employees more clearly, helping teams find key details faster.
Original PR description
Purpose ======= Setup a kanban view to easily jump to scheduled calendar events of type online appointments. Specification ========== set kanban as default view https://nimb.ws/bMDBLP in listview, add 'location' field after 'name' + set many2many_tags widget on 'employee_ids'
Financial reports can now be filtered by operating unit, giving businesses a clearer view of results for specific operational areas. If no operating unit is selected, reports continue to show the relevant company data, while selected units narrow the report to matching records.
Original PR description
Task: https://www.odoo.com/web#id=1917619&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.9da01f115c928cde4b8eb85243999c84 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 makes key parts of the asset form easier to target for future customizations. It does not change day-to-day functionality, but it reduces effort and risk when adapting the asset form to specific business needs.
Original PR description
Right now the `form` view has a lot of elements (also a lot are nested) and it is not really easy to `xpath` into the deeper elements. Some `name` on the most important elements allow to easily xpath from there on.
The customer follow-up form has been updated with a clearer sheet-style layout. This makes the screen easier to read and more consistent with other Odoo forms, improving day-to-day usability for accounting teams.
Original PR description
Before this PR:  After this PR: 
Field Service projects are now easier to configure with one setting that prepares billing, timesheets, worksheets, and planning defaults automatically. Task screens and buttons were cleaned up so users better understand the next step and avoid confusion between regular project work and Field Service workflows.
Original PR description
This merge brings small and big changes related to the flow of an FSM tasks and the FSM project configuration. * task flow - clean views in order to make the user better understand what is the next…
This merge brings small and big changes related to the flow of an FSM tasks and the FSM project configuration. * task flow - clean views in order to make the user better understand what is the next step to do in the FSM flow. - better split project and FSM buttons on task form view. The goal is to avoid confusion in user mind. A task can be FSM and follow the flow of the project app (stage by stage), and simutaneously follow the FSM flow (draft, sent, billed, done). * FSM project config In order to simplify this, we introduced the 'is_fsm' flag. Checking it on a project preconfigure the settings for the project to be in FSM mode. An FSM project is a "task rate" billable project with timesheets and worksheets. To do so, we - introduce the 'is_fsm' flag, and the onchange forcing the configuration - remove "allow planning": the gantt view and planned dates on task form view are always visible. This is not an option anymore. - remove "allow billable": we now use the flow of "task rate", meaning the project can not be billable, but each task is at a different rate (the one of the generated sale order line linked to the task, based on the service product of the project). Task-2009567
Referral levels now display their images directly instead of showing file attachment details, making the referral setup screens clearer for users. The update also adds internal labels to key screen elements, helping future changes and customizations be made more reliably.
Original PR description
This PR changes two things: 1. It adds the image widget on the referral levels as it was now just showing the attachment name in KB, not the image itself 2. Add `name` on the main elements for easier `xpath` expressions in the future @mart-e are you the one to review/approve this? Or should I have @RomainLibert or @tivisse? They seem to have made the app.