Daily updates from Odoo
Thursday, May 8, 2025
7 changes · master
New functionality added to Odoo
Users can now save attachments from any chatter or chat directly into their Documents “My Drive” area. This makes it easier to keep important files without downloading and re-uploading them, improving day-to-day document handling.
Original PR description
**Purpose:** Enable users to add attachments from any chatter or chat directly to their "My Drive" in the Documents module. **Specifications:** Include an "Add to My Drive" button alongside the download and delete buttons in attachments to make it easy for users to add them to their drive.  Task-4236980
Enhancements to existing features
The website setup flow has been refined to make onboarding clearer and more polished for users creating a new website. This should help new users move through the configurator with less friction and a better first impression.
Original PR description
task-4505899
The Sign sharing flow was updated to make the share wizard clearer while preserving the existing ability to manually stop sharing documents. This improves the user experience around shared signature documents, though expiration dates for shares are still not available.
Original PR description
Before this commit, when sharing a document, you could only stop sharing manually using the Stop Sharing option. Unlike other documents, there was no option to set an expiration date for shared documents. With this commit, the ability to manually stop sharing documents using the Stop Sharing option remains. However, the option to set a validity period like with other document types, is still not available. task-4163986
Users now receive a warning when changing a contact’s email address if that contact has pending signature requests. This helps prevent important signing documents from being silently sent to a new email address without confirmation.
Original PR description
Before this commit, when the email address of a res.partner was changed, any pending sign requests were automatically sent to the new email without notifying the user. With this commit, a warning is displayed when the email address is updated: "There are pending sign requests for this contact. Would you like to send them to the new email address?" Task-4570835
Brazilian localization now supports external tax calculation and electronic document submission for vendor bills and vendor bill refunds. This helps businesses handle cases where the customer must pay taxes on supplier bills that are not charged directly by the vendor.
Original PR description
This does both tax calculation and EDI for vendor bills and vendor bill refunds. It's needed because in certain cases the customer will pay a specific tax on bills that is not directly charged by the…
This does both tax calculation and EDI for vendor bills and vendor bill refunds. It's needed because in certain cases the customer will pay a specific tax on bills that is not directly charged by the vendor. Luckily, not many changes are needed to adapt the tax calculation and EDI code for invoices to work on bills as well. The most important ones are changing the operation type and allowing to use the account.move.send wizard to work with bills. Because this needs to change what `move_type`s an external tax calculator acts on, we take the opportunity to absorb those conditions into the `is_tax_computed_externally` field. It simplifies the logic a bit, and makes it easier to change based on the needs of the tax calculator. It means that every tax calculator is now responsible for marking the types of records they act on in a `_compute_is_tax_computed_externally` override. It's necessary because the move_type domain used to be part of the view in *external_tax*, it's not possible to add that check in the default `_compute_is_tax_computed_externally` because then every sale document would be considered eligible for external taxes. task-4608570
The Indian tax reports module now checks that GST numbers follow the required format before sending requests to GST, e-Invoice, and E-Waybill services. This reduces unnecessary external API calls and helps users receive clearer validation feedback when a GST number is invalid.
Original PR description
Currently, we only check if a GST number is present before making API calls for GST, e-Invoice, and E-Waybill services. This allows invalid GST numbers (such as single-character inputs), leading to unnecessary API calls and ambiguous error responses. This **PR** aims to ensure that only valid GST numbers, formatted according to GST specifications, are sent for API requests. **task**-4668014 **Community PR** - https://github.com/odoo/odoo/pull/207888
Resolved issues and error corrections
Shop floor users now see a cleaner workflow for untracked component moves: detailed move lines are hidden and quantity changes are made through an edit action. An undo option lets users reset the component reservation and picked status, reducing mistakes and making corrections easier during manufacturing.
Original PR description
For untracked component moves in the shop floor:
- No longer show move lines
- Show pencil button instead of add button, clicking opens edit quantity
- Apply sets picked (and passes check if applicable)
- No remove button, instead:
- Add an undo button to unreserve and reassign the move, and set picked to false (and sets quality status to none on check if applicable)
task-4760982