Monday, February 17, 2025
15 changes · master
New functionality added to Odoo
Amazon sellers can now select the Ireland marketplace directly in Odoo. This removes the need to add Amazon.ie manually and makes setup easier for Irish marketplace operations.
Original PR description
**Description of what this PR addresses:** - Add amazon marketplace for Ireland(IE) **Desired Behaviour after PR is merged:** - Users can access Amazon.ie marketplace directly without adding manually. Task-4447381
Enhancements to existing features
Approval activity updates now send only the information needed instead of all available activity fields. This reduces unnecessary data transfer and supports cleaner, more efficient activity handling across related apps.
Original PR description
Currently the _to_store of mail.activity is actually returning all fields (just using read() result). In order to improve _to_store and also to reduce the number of useless fields we send, we should actually list only the fields we need (also taking care of overrides if necessary). In a similar pattern as other _to_store methods. PR community: https://github.com/odoo/odoo/pull/189598 Task-4364655
This update adds more realistic appraisal demo data for the Indian payroll module using dates that stay current over time. It helps salespeople and business analysts present smoother, more accurate demonstrations to customers and partners.
Original PR description
The purpose of these demo data is for our salesperson or business analyst to give a demo to customers/partners. This PR includes the following changes: - Create demo data for appraisal by adding dynamic date calculations. - Ensured accurate demo data creation for better testing and simulation. task-4231194
This update strengthens automated checks for inter-company sales and purchase flows by verifying that planned dates update correctly. It helps reduce the risk of scheduling issues between related companies, with no direct change expected for end users.
Original PR description
In this commit: ================= - Updated the test case to ensure the planned date changes correctly. Task - [4321341](https://www.odoo.com/odoo/my-tasks/4321341)
Resolved issues and error corrections
Fixed an installation issue in the accounting spreadsheet dashboard caused by a changed dependency order between accounting modules. This helps ensure the dashboard module can be installed reliably without blocking setup due to a missing menu reference.
Original PR description
Since enterprise#77895 the module 'accountant' depends on 'account_reports', whereas it was the contrary before. And so this module installation was raising an error on unknown reference 'accountant.menu_accounting' runbot error 116839
Code cleanup and technical improvements
Social post actions such as loading comments and liking posts or comments now call the post record directly instead of going through separate web endpoints. This simplifies the internal flow, reduces duplicated routing code, and should make the social integrations easier to maintain without changing the user experience.
Original PR description
Before this commit: - we used to follow an approach where to get the comments made on a post, like that comment, like a post, etc, we were making an `rpc` call to the controller bound on a specific route. - say `/social_facebook/like_comment` to like a comment present inside a post. - the controller method then used to fetch the related `social.stream.post` record, and call the actual method. ex --> `stream_post._facebook_like(comment_id, like)` After this commit: - we now directly call the method bound on the related `social.stream.post` record bypassing the controller calls. Task-**4184961**
Miscellaneous changes
Fix the position of the web ribbon which isn't correctly set to the right of the kanban card. related PR: odoo/enterprise#77884 Task-4582362 Forward-Port-Of: odoo/enterprise#79437
Original PR description
Fix the position of the web ribbon which isn't correctly set to the right of the kanban card. related PR: odoo/enterprise#77884 Task-4582362 Forward-Port-Of: odoo/enterprise#79437
Before this commit: Total weight sent for a multipackage shipment was sum of all the weights of packages in the shipment. After this commit: Average weight of all the packages is sent as total weight. Sendcloud in the backend use average weight for the multipackage shipping request and multiplies it by the number of packages. *checked with sendcloud support. opw-4260104 Forward-Port-Of: odoo/enterprise#79001
Original PR description
Before this commit: Total weight sent for a multipackage shipment was sum of all the weights of packages in the shipment. After this commit: Average weight of all the packages is sent as total weight. Sendcloud in the backend use average weight for the multipackage shipping request and multiplies it by the number of packages. *checked with sendcloud support. opw-4260104 Forward-Port-Of: odoo/enterprise#79001
steps to reproduce: - Install the module approvals_purchase - As admin user - go to approvals - create a new approval for RFQ request - attribute the approval to an user without any access rights - put yourself as the approver - submit and validate the approval - click on the button Create RFQ's - create the RFQ - logout and connect as the user without access rights - try to access your approval -> Access Error related infos: first appeared with: https://github.com/odoo/enterprise
Original PR description
steps to reproduce: - Install the module approvals_purchase - As admin user - go to approvals - create a new approval for RFQ request - attribute the approval to an user without any access rights -…
steps to reproduce: - Install the module approvals_purchase - As admin user - go to approvals - create a new approval for RFQ request - attribute the approval to an user without any access rights - put yourself as the approver - submit and validate the approval - click on the button Create RFQ's - create the RFQ - logout and connect as the user without access rights - try to access your approval -> Access Error related infos: first appeared with: https://github.com/odoo/enterprise/commit/4220723e0779287e5a8e301553e1a870cd3c4ca5 in task: 2040710 Reason: No group where set on the button 'Purchase Orders' which is used to access the RFQ from the approval this button needs a protected field to be able to be displaed properly in addition to that no default value was set if the user has no rights to read the 'purchase.order.line' model. Expected behavior: The button should not be displayed if the user has no access rights to the RFQ and thus grand access to the approval of the user FIX add a default value if the user has no read rights on the model 'purchase.order.line' ultimatly making everything related to it in the form view invisible Also add a group to it in the view to permit to remove the default value in master task-3561514 Forward-Port-Of: odoo/enterprise#79098 Forward-Port-Of: odoo/enterprise#78275
### Steps to reproduce: - Create a recurring product with only one recurring plan - Go to the product's page in the website - Notice the pricing table is shown with only one plan ### Cause: In the pricing view in the website we are showing the pricing table just after checking if we have pricings or not. ### Fix: We are now checking if the pricings we have is more than one we will show the table otherwise will not show it. opw-4559071 Forward-Port-Of: odoo/enterprise#79102
Original PR description
### Steps to reproduce: - Create a recurring product with only one recurring plan - Go to the product's page in the website - Notice the pricing table is shown with only one plan ### Cause: In the pricing view in the website we are showing the pricing table just after checking if we have pricings or not. ### Fix: We are now checking if the pricings we have is more than one we will show the table otherwise will not show it. opw-4559071 Forward-Port-Of: odoo/enterprise#79102
Before this commit, the under warranty field is always copied when the user duplicates a task which it does not make sense since the new task could not have exactly the same context and the intervention could be different. This commit avoid copying the under warranty field when the user duplicates a task to let the user decide if the new task should be also in warranty or not. opw-4571460 Forward-Port-Of: odoo/enterprise#79250
Original PR description
Before this commit, the under warranty field is always copied when the user duplicates a task which it does not make sense since the new task could not have exactly the same context and the intervention could be different. This commit avoid copying the under warranty field when the user duplicates a task to let the user decide if the new task should be also in warranty or not. opw-4571460 Forward-Port-Of: odoo/enterprise#79250
isActive: ["auto"] doesn't make sense with the "run" function in a step because tour_interactive doesn't take into account steps without the "run" function. So, in this commit, we remove all isActive: ["auto"] for steps where there is no "run" function. Forward-Port-Of: odoo/enterprise#79291 Forward-Port-Of: odoo/enterprise#79068
Original PR description
isActive: ["auto"] doesn't make sense with the "run" function in a step because tour_interactive doesn't take into account steps without the "run" function. So, in this commit, we remove all isActive: ["auto"] for steps where there is no "run" function. Forward-Port-Of: odoo/enterprise#79291 Forward-Port-Of: odoo/enterprise#79068
Bug === In some situation, it's possible that the `is_template` raises when it shouldn't. It's more consistent to check it after the creation (super call). Task-4571151 Forward-Port-Of: odoo/enterprise#79173
Original PR description
Bug === In some situation, it's possible that the `is_template` raises when it shouldn't. It's more consistent to check it after the creation (super call). Task-4571151 Forward-Port-Of: odoo/enterprise#79173
Steps to reproduce ============= 1. Allow edit access to portal user. 2. Try to publish an article from the portal user. The portal user has no right to publish/unpublish articles. After this commit ============== This commit prevents access error when portal users try to publish an article. Task-4414401 Forward-Port-Of: odoo/enterprise#79258 Forward-Port-Of: odoo/enterprise#76350
Original PR description
Steps to reproduce ============= 1. Allow edit access to portal user. 2. Try to publish an article from the portal user. The portal user has no right to publish/unpublish articles. After this commit ============== This commit prevents access error when portal users try to publish an article. Task-4414401 Forward-Port-Of: odoo/enterprise#79258 Forward-Port-Of: odoo/enterprise#76350
With is Commit : ---------------------------------------------------------- - In the previous implementation, components marked for manual consumption were automatically consumed, like auto-consumed components, when starting production on a manufacturing order (MO). This occurred due to missing logic and conditions in the code that failed to differentiate between manual and automatic component consumption, and it only affected the shop floor operations. - This update corrects the components
Original PR description
With is Commit : ---------------------------------------------------------- - In the previous implementation, components marked for manual consumption were automatically consumed, like auto-consumed components, when starting production on a manufacturing order (MO). This occurred due to missing logic and conditions in the code that failed to differentiate between manual and automatic component consumption, and it only affected the shop floor operations. - This update corrects the components' consumption process and enhances production tracking's reliability, ensuring that manual components are managed according to their intended usage. Task id: 4096514 Community PR: odoo/odoo#175816 Forward-Port-Of: odoo/enterprise#79277 Forward-Port-Of: odoo/enterprise#77831