Daily updates from Odoo
Tuesday, February 19, 2019
5 changes
Enhancements to existing features
The project settings page has been reorganized with a new grouping area so related options can be placed more clearly on the right side. This supports a cleaner setup experience and prepares the layout for additional enterprise settings.
Original PR description
Add a new group in the settings page, allowing to put some others settings on the right side of the page (needed in enterprise). Task-1942377 Closes #31212 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Chat and Discuss autocomplete lists now automatically highlight the first suggestion. This makes it faster for users to navigate and select contacts or channels using the keyboard.
Original PR description
Task:https://www.odoo.com/web#id=1894447&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad:https://pad.odoo.com/p/r.11840c36adae746affa5f56b44d4612a -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change makes Odoo's browser-based automated tests look for clear success and failure messages instead of generic words that can appear during normal use. It reduces false test failures and improves diagnostic logging, helping teams maintain quality with fewer misleading test results.
Original PR description
When evaluating js tests using the browser_js method, they are considered a success when 'ok' is found in the console log and a failure if 'error' is found instead. This is not very robust and…
When evaluating js tests using the browser_js method, they are considered a success when 'ok' is found in the console log and a failure if 'error' is found instead. This is not very robust and recently failed with this commit : 7410de111fe It adds a filter named 'Error' in a view, when the 'click_all' test clicks on this filter, a message with the name of the filter is written in the console, wrongly leading to a test failure. With this commit, the browser_js method expects a log message in the browser console with the explicit text "test successful". On the other hand, any error in the console log will lead to a test failure but a test can be forced to fail with the explicit error message in the browser console "test failed". As a bonus, the python logger should now also log browser js trace messages. 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
This update makes an internal online learning method private, reducing the chance it is used incorrectly by other parts of the system. The change is technical housekeeping and should not affect how users create, manage, or view eLearning content.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: @odony Another conflict for @Elkasitu -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Adds demo payroll data so the Belgian individual account report can be tested more easily for a full year. This helps ensure the report works reliably when all yearly payslips are required.