Daily updates from Odoo
Monday, March 18, 2024
14 changes
1 change
Enhancements to existing features
This update automatically fills the PAN number when a GSTIN is entered, streamlining the process for users in India. Previously, users had to manually input the PAN, even after providing the GSTIN, leading to potential errors. This change simplifies tax compliance and reduces manual data entry.
Original PR description
Previously, users were required to enter their PAN number even after manually inputting their GSTIN, even though the PAN is inherently part of the GSTIN (spanning from the 3rd to the 12th character). Furthermore, there was no mechanism to alert users if the manually entered PAN did not match the PAN segment within the GSTIN. This commit automates the filling of the PAN based on the entered GSTIN. Now upon entering a GSTIN, the corresponding PAN is auto-filled. Task link: https://www.odoo.com/web#model=project.task&id=3767627 task-3767627 Forward-Port-Of: odoo/odoo#157006
7 changes
Enhancements to existing features
This update standardizes the wording from “canceled” to “cancelled” across Helpdesk, Field Service, timesheet-related Helpdesk sales views, and Sales Planning. It improves consistency in customer-facing labels and messages without changing functionality.
Original PR description
*=helpdesk_fsm,helpdesk_sale_timesheet This PR renames the remaining occurrences of "canceled" to "cancelled". Task-3713873
The Planning app receives several usability improvements that make scheduling clearer and easier to act on. Users get clearer email wizard wording, better filters, improved popovers and progress displays, more helpful overlap warnings, and quick actions in their planning list.
Original PR description
*_ = planning_holidays, project_forecast, project_forecast, project_timesheet_forecast, sale_planning, sale_timesheet_enterprise, timesheet_grid, web_gantt Purpose of this PR is to improve the generic UX of the planning app. So, in this PR: - change send planning by email wizard names. - rename filter name from non billable to non-billable. - set placeholder for the planning_role_ids. - make 'plan services' false when creating services on the fly. - add start_date and end_date filter. - improve front-end popover UI. - change progress bar value hour format. - change Gantt view progress bar warning. - add a button in the list view of my planning. - change overlap slot message task-2962840
The product catalog has been adjusted so it can better support more complex business flows, such as adding catalog items into different sections that share the same parent or base record. This makes it easier for future Odoo features and customizations to reuse the catalog in manufacturing, field service, and sales-related scenarios without duplicating logic.
Original PR description
- Take arguments passed into product catalog related rpc calls into a separate function to make them patchable. - Add kwargs to product catalog mixin methods in order to allow more versatility with passing arguments Use cases: - Adding product catalog to sections having same parent (e.g. components and byproducts inside mrp.bom) - Adding product catalog to sections having same base model (e.g. components and byproducts inside mrp.production are both stock.move) - etc In such cases it is convenient to pass an extra arguments referring to child model or parent model to handle differences on the backend. Task: 3640422
Peruvian invoice PDFs now include the SPOT withholding amount and the bank account where customers must make the related payment. This makes required payment information visible directly on the invoice document instead of only in the electronic XML file, reducing confusion and helping customers pay correctly.
Original PR description
In Peru we have the SPOT system, where a customer may have to pay a withholding on the invoice he receives in a specific bank account. Currently some of the required information is only available in the XML of the electronic invoice, but not on the PDF representation. In this commit, we add the withholding amount and the bank account number on which they have to pay to the PDF, as well as format all the information in a clear way. [task-3413744](https://www.odoo.com/web#id=3413744&model=project.task&view_type=form&cids=1)
Austrian financial reports were updated so their labels and report codes are clearer and better translated. The change also adds missing accounts to reduce empty report categories, improving report completeness for local accounting users.
Original PR description
Changed from tag formula to code formula. Added new accounts to fill empty categories. Translated everything to English, with po/pot added for German Should be good except 22-23-24 where I don't know what to do
Messaging channels now avoid updating every member whenever a new message is posted. This improves scalability and responsiveness for large conversations, including WhatsApp-related discussion channels, without changing the intended user experience.
Original PR description
In `message_post()`, there is a LOC to write to all members of the channel on `is_pinned` and `last_interest_dt`, which cannot possibly scale well.
This commit removes the writing to all members and instead uses:
1. add `channel.last_interest_dt` and only do writing to the channel
when doing the `message_post`.
2. remove writing to the `channel_member.is_pinned` and add
`channel_member.unpin_dt`. Making the `is_pinned` a computed field
instead.
task-3624265
https://github.com/odoo/odoo/pull/155569Chilean and Dutch accounting reports were updated to keep working after underlying account fields were changed from stored values to calculated values. This helps maintain accurate reporting while also standardizing related accounting query handling to avoid formatting issues.
Original PR description
The fields `include_initial_balance` and `internal_group` are not stored anymore.
6 changes
Enhancements to existing features
This update improves how Odoo fetches bank statements from CodaBox when users have multiple bank accounts. Previously, the system would download files based on the oldest inactive account, resulting in unnecessary downloads of old statements. Now, each account tracks its own last statement date, allowing the system to fetch only relevant recent files for each account separately. This makes the import process faster and more efficient.
Original PR description
Currently we send a list of ibans, and a single date from which to fetch the files. This is a bit problematic if the user has multiple journals and one of which is not used. In such a case, this old journal won't have transactions for months. Then we'll use the date of this old journal as the one from which to start fetching. So a journal that is up to date and gets documents everyday will still use this old date. Therefore we'll download lots of files (3 months or historic) even though the vast majority will not be used (only skipped because already imported) From now on, for each journal, we send the date of the last bank statement along with the IBAN of the journal, so that on IAP's side, we can filter out older bank statements. This allows faster fetching of the files. IAP: https://github.com/odoo/iap-apps/pull/771 task-id 3762743
IoT devices can now automatically send their logs to the Odoo server instead of requiring manual log file collection from customers. This improvement enables faster support troubleshooting by eliminating the need for customers to manually retrieve and share IoT logs, which previously required on-site access to the local network. The feature can be toggled on or off through the Handlers configuration page.
Original PR description
Before this commit: IoT logs are kept in an IoT log file. Any time the support would need IoT log information, we are forced to ask the customer to send it to us as it requires to be in the LAN.…
Before this commit: IoT logs are kept in an IoT log file. Any time the support would need IoT log information, we are forced to ask the customer to send it to us as it requires to be in the LAN. After this commit: Relevant* log lines will be automatically send out to the server using an HTTP route. This feature can be toggled within the Handlers list page  preview:  *: Relevant = - Any odoo logs (depending on the level set in the handlers list, see: https://github.com/odoo/odoo/pull/134174 ) - Any other logs (werkzeug, python libraries, etc.) except /hw_proxy/hello Note: IoT logs received by the server will ALWAYS be logged regardless of it level. So an Odoo server set in INFO which receive a DEBUG log from the IoT will log it in its log with the DEBUG level Related odoo PR: https://github.com/odoo/odoo/pull/150920 opw-3696519 Forward-Port-Of: odoo/enterprise#57836 Forward-Port-Of: odoo/enterprise#55055
This update improves how event registration confirmation emails are sent by allowing them to be processed asynchronously instead of immediately. When many people register for an event at the same time, this change prevents the system from slowing down by deferring email generation to scheduled background tasks. This is especially beneficial for events with high registration volumes.
Original PR description
This PR introduces a new configuration parameter 'event.event_mail_async' forcing registrations-based communication to be asynchronous. Instead of directly sending communication it triggers the cron to be run as soon as possible. When having large volume of registrations, and especially concurrent registrations it saves a DB to avoid generating tickets and preparing emails synchronously to the registration creation. Task-3764894: Event: Allow using cron triggers for communication Part of Task-3084943: Event: Improve communication scheduler scalability
IoT devices can now automatically send their logs to the central server instead of requiring manual log file collection from customers. This improvement enables faster support troubleshooting by eliminating the need for customers to manually share IoT logs, and includes a toggle to enable or disable this feature from the Handlers configuration page.
Original PR description
Before this commit: IoT logs are kept in an IoT log file. Any time the support would need IoT log information, we are forced to ask the customer to send it to us as it requires to be in the LAN.…
Before this commit: IoT logs are kept in an IoT log file. Any time the support would need IoT log information, we are forced to ask the customer to send it to us as it requires to be in the LAN. After this commit: Relevant* log lines will be automatically send out to the server using an HTTP route. This feature can be toggled within the Handlers list page  preview:  *: Relevant = - Any odoo logs (depending on the level set in the handlers list, see: https://github.com/odoo/odoo/pull/134174 ) - Any other logs (werkzeug, python libraries, etc.) except /hw_proxy/hello Note: IoT logs received by the server will ALWAYS be logged regardless of it level. So an Odoo server set in INFO which receive a DEBUG log from the IoT will log it in its log with the DEBUG level Related enterprise PR: https://github.com/odoo/enterprise/pull/55055 opw-3696519 Forward-Port-Of: odoo/odoo#155944 Forward-Port-Of: odoo/odoo#150920
The Indian localization module now automatically fills in the PAN (Permanent Account Number) field when users enter a GST number, since the PAN is already embedded within the GST number. This eliminates duplicate data entry and reduces the chance of mismatches between the two fields, making the process faster and more accurate for Indian businesses.
Original PR description
Previously, users were required to enter their PAN number even after manually inputting their GSTIN, even though the PAN is inherently part of the GSTIN (spanning from the 3rd to the 12th character). Furthermore, there was no mechanism to alert users if the manually entered PAN did not match the PAN segment within the GSTIN. This commit automates the filling of the PAN based on the entered GSTIN. Now upon entering a GSTIN, the corresponding PAN is auto-filled. Task link: https://www.odoo.com/web#model=project.task&id=3767627 task-3767627 Forward-Port-Of: odoo/odoo#157006
This pull request updates the Account module with improvements to logos, login templates, and custom addons configuration. The changes include updates to multiple language translation files and module manifest, ensuring the accounting system is properly localized and branded across all supported languages.
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