Daily updates from Odoo
Navigate
Branch
Tuesday, July 2, 2019
14 changes
Enhancements to existing features
The recruitment app is updated to make job applications easier to navigate, including cleaner menus and a quicker way for recruiters to find their own job positions. This also improves internal test tagging so development teams can run more targeted automated tests.
Survey answer forms now display which attempt a response represents, such as attempt 2 of 4. This helps staff understand a respondent's progress and retry history without extra investigation, while avoiding performance issues in broader list views.
Original PR description
Purpose ======= This commit adds the attempt number on the answer (= survey.user_input) form view. The attempt number is always relative to its "pool" of attempts and depends on the "invite_token" if specified. ex: Attempt n° 2 / 4 (where "4" is the attempts_limit of the related survey). This information is only displayed in the form view because it can't be computed in batch and would badly impact the performance of the list view. 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 edit field translations in a popup without leaving the form they are working on. This makes translation updates faster and more convenient, while also handling English translations more consistently with other languages.
Original PR description
Another alternative of #31090 and #33473 without a wizard Task-id: 1892031 (pad irrelevant) cc @odony this way it is still possible to use the search view on the list of translations
This update prepares Odoo's SMS features for upcoming enhancements by improving phone number handling, adding batch SMS sending support, and strengthening automated SMS testing. It should make future SMS changes safer and more reliable without creating major immediate changes for users.
Original PR description
Purpose of this merge is to prepare upcoming SMS refactoring by already pushing some tools, cleaning and tests in master. Contained in this merge * improvement of phonenumbers library tools and usage in SMS; * addition of SMS test classes with tools and mocks; * addition of SMS tests; See sub commits for more details. Related to task 1922163.
Stock quantity lists now adapt better to the product being viewed by hiding unnecessary lot or product fields when they do not apply. The update quantity flow and empty-state messaging were also restored or clarified, making inventory adjustments easier for users with simpler stock setups.
Original PR description
On the editable list quant view, when user come from a non tracked product view, the `lot_id` field is hide. Task #2006337 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now edit translated field values directly from the view through a simple wizard, including from list views. This makes translation work more accessible and reduces the need to navigate through less user-friendly technical menus.
Original PR description
Description of the issue/feature this PR addresses: - Related task : https://www.odoo.com/web#id=1892031&action=327&model=project.task&view_type=form&menu_id=4720 - Pad: https://pad.odoo.com/p/r.e7d2d6bd2e869b77fb0b4c2818489e3b Current behavior before PR: - Field translation was not user friendly. Desired behavior after PR is merged: - Field translation will be user friendly and user can edit the translation value also from the tree view. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale setup is made smoother by automatically assigning the right sales journal and keeping key pricing options visible. Businesses using only Point of Sale can now manage discount display policies on pricelists without needing the Sales app, reducing setup friction and configuration mistakes.
Original PR description
1. Default PoS Orders Journal Make sure that a default POS order journal is created and set as default sales journal on the newly created pos.config 2. PoS Orders https://nimb.ws/I1sp7F…
1. Default PoS Orders Journal
Make sure that a default POS order journal is created and set as default sales journal on the newly created pos.config
2. PoS Orders
https://nimb.ws/I1sp7F
https://nimb.ws/GKmwo5
3. In the PoS.config
Always show the default pricelist (by default, no matter what advanced settings are used).
https://nimb.ws/2cv3H4
4. On pricelist:
The field discount_policy has been moved from 'sale' to 'product' in revision: https://github.com/odoo/odoo/pull/27310/commits/a216473c73086cf028228d2d5cf3470c8a8d55bc but the view is still only there in sale module, meaning that if you have only point of sale installed, you have no way to enable this on the pricelist and so use it in POS. Move the view in module 'product' and apply correct groups.
If the advanced pricelists are activated : https://nimb.ws/hcRrmt
Show this setting on the pos config : https://nimb.ws/kYzTtJ
If ticked, https://nimb.ws/7vFOT4
Default pricelist and advanced pricelists should be next to each other
5. Define a domaine for the pos orders journal in pos.config : should be a sales journal
task: 2008468Users can now edit translated field values from a simple popup opened by the globe icon, instead of navigating away or understanding translation internals. The change makes all languages, including English, appear consistently so translation work is easier and less confusing.
Original PR description
Now pressing on earth icon on translated field will open wizard with editable listview, where user will have only two field: Language and Translation Value The complexity of the translations is…
Now pressing on earth icon on translated field will open wizard with editable listview, where user will have only two field: Language and Translation Value The complexity of the translations is hidden to the user, he no longer needs to know that English is the reference language, all lines seems equal for him (we are using an English line) A simple version with a popup wizard is used (a custom js widget may be used in the future) Remove the `AND l.code != 'en_US'` clause from the SQL query to always create an English translation. This was already the case with the callable translate methods and helps to reduce the arbitrary importance of the en_US language. This is a pick of #31090 @msh-odoo please have a look at the following changes and let me know if I missed something: - simplified the generated domain to 3 clauses only - removed `.with_context(lang='en_US')` in `_prepare_translation_domain` - don't store the related field `value` on `translation.lines` - renamed button and domain variables - changed some `context.get(key)` to `context[key]` to break earlier on missing context keys
Product records without images now skip unnecessary image processing steps. This reduces overhead when creating many products, improving creation speed by about 20% in the measured case.
Original PR description
All of those fields `__get__` and method calls have a cost, it is small but when done for many records it adds up, so they are better not done. For creating 1000 products without image: 47ms +/- 1ms before the commit 37ms +/- 1ms after the commit That's around 20% less. Part of task-1918881
Follower-related updates in the messaging system were optimized to run much faster when many records are processed at once. This improves the speed of creating records in apps that use Odoo's messaging and activity tracking features.
Original PR description
If `self` contains around 1000 records, this reduces the time of the method by a factor of 10. This speeds up the creation of all models using `mail.thread`.
Administrators in debug mode can now see a direct shortcut from a user profile to that user's available menus, including a count. This makes it easier to review or configure menu access, such as when preparing template users.
Original PR description
**Description of the issue/feature this PR addresses:** Adds a smart button with count to see Menus (in debug mode only). It can be useful, for example when creating template user. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Product attribute values are now shown with cleaner, less repetitive names in product setup and search results. This reduces visual clutter for users configuring product variants and makes selecting the right values easier.
Original PR description
Add comment on both methods to clarify their goal. Remove the unnecessary check. Indeed the `product.template.attribute.value` is not displayed during the variant set up of the product template so there is no point to check the context for it. Update the view to apply the context change also for the search result. Indeed the context change on the o2m itself didn't propagate so the attribute was displayed unnecessarily on the search result. 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
Sales quotes and orders created from a subscription upsell or renewal now show a message in the sales chatter linking back to the original subscription. This makes it easier for sales teams to understand the context of an order and quickly access the related subscription record.
Original PR description
Before this - There was no way to know a quote/so come from a upsell/renewal of the subscription. In this - Added chatter msg in Sale Order with link to Subscription. task-49017
Code cleanup and technical improvements
The VOIP phone-related code was reorganized to make future SMS and phone widget improvements easier to deliver. This is an internal cleanup with little immediate change for users, but it helps reduce complexity for upcoming enhancements.
Original PR description
This merge is mainly an enterprise adaptation of community PR https://github.com/odoo/odoo/pull/34516. See sub commits for more details.