Friday, September 9, 2022
17 changes · master
Enhancements to existing features
The mail emoji picker now shows a dedicated no-results screen when a search does not match any emoji. This makes the interface easier to understand and helps users quickly see that they need to adjust their search.
Original PR description
Task-2976156
This update improves the mail module by removing an unnecessary database operation that could slow down some requests. Users should see slightly better performance in affected mail-related workflows, with no expected change in functionality.
This change reorganizes how customized accounting reports plug into Odoo, reducing the chance that different report customizations conflict with each other. It should make future local or specialized report changes easier and safer to maintain, without changing the core reporting experience for business users.
Original PR description
In Reportalypse, custom reports use fields to refer to functions allowing customizing different behaviors of the engine. With this, all account.report models contain all the functions of all the custom reports, leading to possible name clashes if the functions aren't properly prefixed. We can improve that a little: instead of having multiple fields, we use but one, referring to an AbstractModel inheriting from a new AbstractModel called account.report.custom.handler. This AbstractModel simply contains the different functions that can be overridden, and its subclasses are responsible to do so. In the code, instead of calling _get_custom_report_function, we check whether there is a custom handler for the report, and call the right function on it. task-2954761 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The mail app now handles the state for adding items in the Discuss view instead of the broader Discuss model. This internal cleanup reduces unnecessary computed-field updates, helping keep the messaging interface more reliable and easier to maintain.
Original PR description
This move will remove the need of the adjustment compute and therefore will avoid writing on computed fields.
The live chat button and chat window are now hidden when users are editing a website. This keeps the editing workspace cleaner and prevents the chat widget from getting in the way while designing pages.
Original PR description
Currently, when the website editor is opened, the LiveChat window/button is visible. After this PR, the LiveChat button/window will be hidden in the website editor. TaskID: 2824363
This update improves how internal test errors are reported for mail-related code, making failures easier for developers to diagnose. It also reduces misleading error output in automated testing, helping teams identify the real cause of failed checks more quickly.
Original PR description
Before this commit the error raised/logged when rejecting the afterEvent promise was imcomplete. This is due to the fact we're creating the error inside the promise itself. In order to get a better stack trace, the error is now declared outside of the promise. Moreover, both `afterNextRender` and `afterEvent` functions were using `console.error` before rejecting the promise. This is also a problem since runbot will show the error printed by `console.error` instead of the one of the test failure. In order to solve this issue, those two `console.error` have been replaced by `console.warn`.
This update tidies older internal code behind activity displays in the Mail app. It should make future maintenance easier without changing day-to-day user workflows.
Original PR description
In preparation of future clean up. - move BasicActivity to KanbanActivity (only usage of that abstract class) - remove useless class o_activity_link - remove useless class o_activity_label - move d-flex from o_activity_title_entry to template - move align-items-baseline from o_activity_title_entry to template - move o_no_activity SCSS to template - clean selection compute - clean record_id - clean activityState, _setState, _reset - remove obsolete unlink activity code https://github.com/odoo/enterprise/pull/31201
The web editor's code view now has a minimum height, making it easier to read and edit code. This reduces frustration for users who switch to code view and previously saw a very small editing area.
Original PR description
The editor's code view had no minimum height so it was impractically small. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website content lists for products, events, and courses have been simplified by hiding less-used columns and improving column placement. This makes site management screens easier to scan while keeping extra details available when needed.
Original PR description
*: event, website_event, website_sale, website_sale_stock, website_slides With [1], new list views were created in the website app to display all key models in the "Site" menu. Each view is based on the related model base view in their related app, with some more website-related fields (like the content URL, the SEO optimization, ...), etc. This commit simplifies those views by removing some columns (make them optional) to not make them feel bloated. Some changes were done in the base views. - Products: simplify the website view by hiding 5 columns. Two were stock related so it had to be done in a new view in website_sale_stock. - Events: simplify the website view by hiding 3 columns. Also move the "stage" column at the end, in the base view too. - Courses: simplify the view by hiding 1 column, this change is done in the base view. [1]: https://github.com/odoo/odoo/commit/da3f4c2aff92cca23ca2d7a87fa0eb5b1d7ce5fe
Project names in task and timesheet lists are no longer clickable links to the project setup screen. This keeps day-to-day list views focused on work entry and avoids sending users into configuration pages they typically do not need after setup.
Original PR description
Before this commit, the project field in task and timesheet models is clickable in list view of those models. This commit prevents to open the form view in the list view since the form view of project is now more a view to configuration the project and so once the configuration is done, the user will not always need to go to that view.
Project fields in field service tasks and planning lists are no longer clickable from list views. This reduces unnecessary navigation to project configuration screens during day-to-day work.
Original PR description
Before this commit, the project field in task and
planning.slot{.template} models is clickable in list view of those models.
This commit prevents to open the form view in the list view since the form view of project is now more a view to configuration the project and so once the configuration is done, the user will not always need to go to that view.The Accounting Import Guide now includes breadcrumbs to make it easier for users to understand where they are and navigate back. This improves usability while keeping the page focused by hiding unnecessary control panel elements.
Original PR description
Currently, the Accounting Import Guide page does not have breadcrumbs. Adding a controlpanel with breadcrumbs for easier navigation, hiding the rest of the elements in the controlpanel.
This update tidies internal layout definitions used by Approvals and Sign activity views. It prepares the codebase for future cleanup without changing business workflows or adding visible features.
Original PR description
In preparation of future clean up. - remove useless class o_activity_link - move d-flex from o_activity_title_entry to template - move align-items-baseline from o_activity_title_entry to template https://github.com/odoo/odoo/pull/99824
Customized financial reports now use a dedicated handler structure instead of mixing all custom behavior directly into every report. This reduces the risk of internal naming conflicts and makes future country-specific and accounting report customizations easier to maintain without changing the user experience.
Original PR description
In Reportalypse, custom reports use fields to refer to functions allowing customizing different behaviors of the engine. With this, all account.report models contain all the functions of all the custom reports, leading to possible name clashes if the functions aren't properly prefixed. We can improve that a little: instead of having multiple fields, we use but one, referring to an AbstractModel inheriting from a new AbstractModel called account.report.custom.handler. This AbstractModel simply contains the different functions that can be overridden, and its subclasses are responsible to do so. In the code, instead of calling _get_custom_report_function, we check whether there is a custom handler for the report, and call the right function on it. task-2954761
The Knowledge app’s sharing prompt now opens links in a new browser tab so users can keep their current work in place. Its portal text is also smaller, making the prompt less distracting while still encouraging sharing.
Original PR description
Purpose ======= Improve the knowledge virality UI done in Task-2936725. Specifications ============== Instead of redirecting the user on their current tab, open a new tab to keep what they were doing. Reduce the portal virality UI text size to make it more discrete. Task-2976493
This change reduces the amount of field information sent to the web client so it receives only what it needs. This can improve efficiency and page loading behavior, with a small related adjustment in Studio.
Original PR description
See the related commit in odoo/odoo for more details.
The Luxembourg reporting module’s expected test results were updated to match current test data. This helps keep automated checks aligned and reduces false alarms during quality validation.
Original PR description
See related community PR.