Monday, March 1, 2021
8 changes · master
Enhancements to existing features
Product list searches that filter by available quantity now use an existing optimization. This should make those searches faster and smoother for users working with inventory data.
Original PR description
Such requests could be done via Products list and there is no reason to don't use optimization --- opw-2452728 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
Accounting journals now keep their outstanding payment accounts when duplicated, reducing manual setup and configuration mistakes. Default account settings are easier to manage, and payment records now provide quicker access to their linked journal entries.
Original PR description
Now when duplicating a bank or cash journal, the outstanding accounts are the same as the original journal. Added a compute method for payment_credit_account_id and payment_debit_account_id to retrieve the default value from the company. These default accounts can be changed in the settings. Change UI for some settings (Default accounts). Added a smart button on payments to access the linked journal entry. Changing the tree view of account.journal: - Edit journal_group_ids: Optional show - Add currency_id: Optional hide - Add code: Optional show - Add default_account_id - Add payment_debit_account_id: Optional hide - Add payment_credit_account_id: Optional hide - Add active **Task ID:** #2451842 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo can now group records using flexible calculated fields that do not need to be stored permanently in the database. This enables more reporting scenarios and improves kanban progress calculations, with large CRM datasets using far fewer queries and loading much faster.
Original PR description
There are few possible reasons why a computable field cannot be storable: 1. it depends on context: * current time * settings of a user (e.g. timezone) * a variable in ``env.context`` 2. a field is…
There are few possible reasons why a computable field cannot be storable: 1. it depends on context: * current time * settings of a user (e.g. timezone) * a variable in ``env.context`` 2. a field is used too rare to be stored in database (e.g. related field to ``partner_id.country_id.name``) 3. it would trigger too many/often recomputations To allow grouping in such exceptional cases, this commit introduces *adhoc* fields, which don't need to be specified in model definition as regular fields. --- As a first application of the new features, this commit also replace read_progress_bar with read_group, which is not just refactoring but a performance improvement too. Test demo crm.lead records: ``` | measurement | before | after | |--------------------+--------+-------| | number of queries | 10 | 3 | | query time, ms | 10 | 5 | | remaining time, ms | 35 | 9 | Test on 20K crm.lead records: | measurement | before | after | |--------------------+--------+-------| | number of queries | 184 | 3 | | query time, ms | 900 | 165 | | remaining time, ms | 5500 | 12 | ``` --- task-1915411 task-2155109 opw-2346901 closes #29292 closes #41421 closes #65136 closes #65854
Appraisal feedback now displays only the survey answers tied to the specific appraisal being reviewed, rather than mixing in responses from the same template. When requesting feedback, the correct survey template is selected automatically, and users without the right access receive a clear access-denied response instead of confusing errors.
Original PR description
Only shows the answers specific for the appraisal requested and not all the answers that are using the same survey template. TaskID: 2465068
Accounting asset lists now show more useful details, such as acquisition date, original value, and depreciation method, while keeping some advanced fields optional. The Online Synchronization menu was also repositioned to make it easier to find, and related accounting settings were reorganized for better consistency.
Original PR description
Changing the tree view of account.asset: - Add parent_id: Optional hide - Add acquisition_date - Add original_value - Add method - Add account_asset_id: Optional hide - Add account_depreciation_id: Optional hide - Add account_depreciation_expense_id: Optional hide Changing the place of "Online Synchronization" menu. **Task ID:** #2451842
Resolved issues and error corrections
People who create or update a project task by emailing the project gateway are now automatically subscribed to that task conversation. This ensures they receive later email replies from colleagues, avoiding missed follow-ups and broken communication loops.
Original PR description
Before this patch if Alice sent an email to the project gateway, she wasn't subscribed to the created (or updated) task. Then, if Bob got her email in his inbox and responded, Bob's message got appended to the task thread, but Alice wouldn't recieve Bob's response in her inbox. After this patch, when Alice creates or updates a task by writing to the project gateway, she will get autosubscribed to that task's thread, making Bob's email responses get to Alice as expected. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @Tecnativa TT19976
This fixes an issue in stock transfers where users could no longer edit the Demand quantity field. The forecast access was changed to use a button instead of an incompatible widget, restoring normal editing while keeping forecast information available.
Original PR description
Following the PR https://github.com/odoo/odoo/pull/62264, it is impossible to edit the Demand field (product_uom_qty) of a stock move in the interface (f.ex when creating an Internal Transfer). The problem came from the forecast widget that was reused but not applicable in case of editable field. A button element is used instead to access the forecasted report. 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
Opening the planning view from an employee record no longer causes an error. This restores reliable access to employee planning information and avoids disruption for users managing schedules.
Original PR description
At first, when we click on view planning in employees it shows the traceback. However, that issue would be solve. Task ID: 2463614