Thursday, November 17, 2022
9 changes · master
Enhancements to existing features
This update brings the spreadsheet engine up to date with multiple fixes that make editing, selection, formulas, and pasted content work more reliably. It also adds a shortcut for inserting links and reduces risks of duplicate sheets or figures, improving day-to-day spreadsheet use in Odoo.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/1b4fac5a [FIX] edition: Handle too long formulas https://github.com/odoo/o-spreadsheet/commit/544cfe68 [FIX] composer:…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/1b4fac5a [FIX] edition: Handle too long formulas https://github.com/odoo/o-spreadsheet/commit/544cfe68 [FIX] composer: Allow to paste text in the composer https://github.com/odoo/o-spreadsheet/commit/f04c7589 [FIX] functions: dichotomicSearch handle 2d array https://github.com/odoo/o-spreadsheet/commit/3660bf27 [REF] components: enforce component autonomy during keyboard event handling https://github.com/odoo/o-spreadsheet/commit/39bb9d88 [IMP] keyboard shortcuts: Insert link https://github.com/odoo/o-spreadsheet/commit/a40186aa [FIX] grid: capture IME altered inputs https://github.com/odoo/o-spreadsheet/commit/a884c78a [FIX] sheet: prevent creation of sheet with the same id https://github.com/odoo/o-spreadsheet/commit/aff05bdd [FIX] figure: prevent duplication of figure id https://github.com/odoo/o-spreadsheet/commit/5c18b6e1 [REF] ranges: make Range immutable object https://github.com/odoo/o-spreadsheet/commit/de5612e3 [FIX] config: Allow to build outside of git repository https://github.com/odoo/o-spreadsheet/commit/b100135c [FIX] grid: remove old component https://github.com/odoo/o-spreadsheet/commit/45f7f714 [FIX] selection: update default selection anchor on dispatched commands https://github.com/odoo/o-spreadsheet/commit/b41a1610 [FIX] selection: don't reset selection on Autofill https://github.com/odoo/o-spreadsheet/commit/16a98748 [FIX] selection: Properly add merge when adding them to the selection https://github.com/odoo/o-spreadsheet/commit/231bbbca [FIX] model: do not replay core commands in ui plugins
Messages in the Mail app are now sent through a queue, making the sending process more reliable and responsive. This helps reduce delays or interruptions for users when composing and sending messages.
Odoo’s mail app now has a dedicated structure for composing messages, making the message writing experience easier to manage and improve over time. This internal improvement supports more reliable and consistent email and chat composition for users.
Original PR description
Task-2390637
This change streamlines how Odoo determines whether messages are historical, require action, or are starred. It helps make mail, chat, notifications, live chat, ratings, and SMS behavior more consistent and easier to maintain, with limited direct impact for end users.
Original PR description
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
Project and task lists now show more useful planning and sales-related information, including deadlines, activity status, creation dates, stage updates, and sales order links. Project updates and portal views were simplified with clearer labels, cropped stage text, and less clutter so teams can review project progress and sales delivery details more easily.
Original PR description
Purpose of the PR is to do the generic improvements for project. So in this PR did the following changes: - add the 'creation date', 'last stage update', 'SOL', 'my deadline' fields in project task list view. - add the 'my deadline', 'next activity' fields in project list view. - crop the label of the stage after x characters in task portal form view. - remove the 'collaborators' stat button from project update right-side panel. - renamed sold->sales, services->sales order items, effective->delivered, remove the totals, include non-service SOLs, increase the size of the SOL column task-2928100
Payment term rules are now automatically ordered by due date, with the remaining balance placed last. This removes a confusing manual step for users and helps invoices follow the intended payment schedule more reliably.
Original PR description
Task [2026399](https://www.odoo.com/web?#id=2026399&action=333&active_id=967&model=project.task&view_type=form&cids=&menu_id=4720) The user should not have to reorder payment term rules, we should order by the number of days and put the balance at the end automatically. (it's too advanced to know you should order lines). -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Event tickets and ticket templates now have a clear manual order when key details like price and event are the same. This makes ticket lists more predictable for users and keeps demo/template data consistently organized.
Original PR description
When the price and the event are the same, nothing allows ordering tickets in event_sale. Therefore, add a sequence number and handle widget to the tickets (in data as well). Also do it for ticket templates. Also, order the tickets (on events and templates) by name before id. Since event type tickets are not linked to any event, the order does not include the event_id. However, event event tickets are, and if they appear in the same list / reporting someday, it makes sense to order them by event_id first. In event_sale, we make sure the price is also in the order. As the price is in the copied fields on the event when using an event template, we add the price on the event type tickets ordering to align with the event event tickets. Add default value to sequence and sequence number to data for event.type model. They were sequenced but demo data had none, hence not really ordered. Also make description optional hide on event types. Task-2997391
Helpdesk and field service users can now see their own deadline directly in list views, making it easier to prioritize daily work. Project update descriptions were also clarified to make progress updates easier to understand.
Original PR description
Purpose of the PR is to do the generic improvements for project. So in this PR did the following changes: - add a 'my deadline' field in fsm, helpdesk ticket list view. task-2928100
Resolved issues and error corrections
This fix ensures Odoo's automated tours and tests fail when real application code has missing dependencies, instead of silently passing. It also cleans up related issues in Live Chat, Website Live Chat, Web reports, and Website Slides so production problems are detected earlier and release quality improves.
Original PR description
*: im_livechat, website_livechat, website_slides In https://github.com/odoo/odoo/commit/c989ff339d1bb8afde3371d12dab8cc227941691, the odoo module system has been changed so that it now errors out…
*: im_livechat, website_livechat, website_slides In https://github.com/odoo/odoo/commit/c989ff339d1bb8afde3371d12dab8cc227941691, the odoo module system has been changed so that it now errors out when modules are defined but have missing dependencies and cannot run. Unfortunately, tours are defined in a single bundle, `assets_tests`, and this bundle is used everywhere tours need to run, but some of these tours depend on modules that only exist in the backend and others on modules that only exist in the frontend. We don't want to break up the `assets_tests` bundle as this creates a poor developer experience, and so the solution that was chosen at the time is that when the `assets_tests` bundle is defined, we ignore all module dependency errors. This causes a problem however, which is that if a module dependency is missing in production code, the page will be broken by the module error (which is expected) but if the `assets_tests` are present, which is the case when running tours and tests, then it won't, meaning the tours will happily pass despite the application being broken, which is unacceptable. This commit fixes this issue by replacing the assets_test bundle by a new bundle (`__assets_tests_call__`) within which all module dependency errors are ignored, which lets dependency errors that are hapenning in other bundles (ie in production code) happen even during the tests. Because of this, this commit also fixes the dependency errors that already existed but were previously silent: - for im_livechat and website_livechat, the code was refactored to use the standard mechanism that we use elsewhere to add data directly in the page: we store the data in __session_info__, and the module that exposes that data is always present, instead of having a module that's defined conditionally, which causes issues when non-conditional modules depend on it. - in web, the `report_assets_common` bundle was used alongside `assets_common` but without `assets_frontend` or `assets_backend`. Reports do not need any js and it appears that it already had what it needed as far as css is concerned except for one fontawesome override. Code was changed so that the js from the bundle is not included and it reports no longer use `assets_common`, the js part of the bundle is no longer used. - in website_slides, the `slide_embed_assets` bundle is used alongside `assets_common` without using `assets_frontend` or `assets_backend` which is required for `assets_common` to function, the approach here was to simply take the files from `assets_common` and remove the files that were causing issues. This bundle should be trimmed at some point, as it contains way too many things that it does not need. The file colors.js was also moved to core, as it isn't graph specific and was causing dependency issues with a field that was importing it.