Daily updates from Odoo
Navigate
Branch
Tuesday, August 24, 2021
9 changes
Enhancements to existing features
Required fields in spreadsheet filter configuration are now easier to spot with a stronger visual border. Error notifications were also improved, helping users understand and resolve missing required information more quickly.
Original PR description
Purpose ======= Improve the UX of required fields in the configuration of spreadsheet filters. Specification ============= Set a bold border on required fields on the global filters side panel. Change the error notification. Task 2342152
Project planning and forecasting screens were refined to make day-to-day project management clearer and easier to use. These updates help teams review forecasts, timesheets, and project information with less friction.
Spreadsheet editing now handles arrow keys more naturally depending on how a cell is opened for editing. This helps users move between cells when expected while still allowing precise text editing after double-clicking, pressing F2, or using the top bar editor.
Original PR description
currently when editing a cell, the arrowkeys will always move the caret through the cell content. this commit changes this behaviour: The directional arrows will move the caret through the cell content, only if the user: -opened the cell composer by double-clicking on it -opened the cell composer by pressing F2 -is editing the content from the topbar composer task-id:2523586
Resolved issues and error corrections
Fixes an issue in Sign where dragging a signature field into the space between two document pages could create the field on both pages. Users now get a single field placement, avoiding accidental duplicates and reducing cleanup during document preparation.
Original PR description
drop only once when a sign item is dropped between two pages before this commit: if a user drops a sign item from the left filed bar to the region between to pages (drop when the dragged sign item has overlap with both pages), the sign item will be added to both pages. taskid: 2623351
This fixes automated tests for Chilean electronic invoicing by ensuring the currencies needed for multi-currency scenarios are active. It helps maintain reliability after a platform change made currencies inactive by default.
Original PR description
since odoo/odoo@4402949 all currencies are inactive by default - activate currencies required for l10n tests
Worksheet-based quality checks now close immediately after the user validates them. This returns operators to the tablet work order view instead of moving them to another quality check, reducing confusion and keeping shop floor workflow focused.
Original PR description
when quality check of type worksheet close the quality check window as soon as the user validates it and return to the tablet view window rather than next quality check.
Code cleanup and technical improvements
This update modernizes JavaScript code across several Odoo Enterprise apps by converting it to a newer module format. It is an internal refactoring intended to improve maintainability without changing how users experience the product.
Original PR description
**Description of the issue/feature this PR addresses:** Convert JS codes into ES6 format 2nd pass, the modules involed are (hr, hr_holidays, sms, snailmail, website_livechat, account_invoice_extract, approvals, documents, mail_enterprise, calendar, crm, mrp, note, website_slides, crm_enterprise, sign, social, voip) No functional change should happen after the refactoring. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Since commit e987fe1, we changed the metrics to compute the happy rating. We should also adapt the corresponding formulas so we keep a correct calculation scale. Now, a "great" rating is scored as 5 instead of 10. If you have only 1 rating, you should anyway expect 100% happy rating. The calculation using the old scoring was : ( 10 / 1 ) * 10 = 100% With the new scoring, before this fix, we are getting : ( 5 / 1 ) * 5 = 25% After the fix, we will get instead : ( 5 / 1 ) * 20 = 1
Original PR description
Since commit e987fe1, we changed the metrics to compute the happy rating. We should also adapt the corresponding formulas so we keep a correct calculation scale. Now, a "great" rating is scored as 5 instead of 10. If you have only 1 rating, you should anyway expect 100% happy rating. The calculation using the old scoring was : ( 10 / 1 ) * 10 = 100% With the new scoring, before this fix, we are getting : ( 5 / 1 ) * 5 = 25% After the fix, we will get instead : ( 5 / 1 ) * 20 = 100% If we divide the scoring by 2, we need to multiply the result in the formula instead of dividing it. opw-2580325 Forward-Port-Of: odoo/enterprise#20399
It was impossible to send an order with the sweden blackbox. We figured out that we sent the vat number instead of the registry company. We corrected the data sent from the js to the driver with the registry company number instead of the vat number. We also added a regex to remove the "-" from the number in the standard format. ex: 556677-1234 -> 5566771234 Forward-Port-Of: odoo/enterprise#20382
Original PR description
It was impossible to send an order with the sweden blackbox. We figured out that we sent the vat number instead of the registry company. We corrected the data sent from the js to the driver with the registry company number instead of the vat number. We also added a regex to remove the "-" from the number in the standard format. ex: 556677-1234 -> 5566771234 Forward-Port-Of: odoo/enterprise#20382