Thursday, October 5, 2023
17 changes · master
Enhancements to existing features
This update brings the spreadsheet component up to a newer version with improvements to data validation, conditional formatting, chart tooltips, and row management. It also fixes several usability and reliability issues, including performance with large sheets, read-only filter controls, find-and-replace behavior, and copy/paste handling across sheets.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/c46de914 [REL] 16.5.0-alpha.9 https://github.com/odoo/o-spreadsheet/commit/1438e657 [FIX] side panels: fix link button…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/c46de914 [REL] 16.5.0-alpha.9 https://github.com/odoo/o-spreadsheet/commit/1438e657 [FIX] side panels: fix link button style Task: / https://github.com/odoo/o-spreadsheet/commit/f66c9ab4 [FIX] components: fix some button styles Task: / https://github.com/odoo/o-spreadsheet/commit/62718580 [IMP] CF: reorder preview list with drag and drop Task: 3504521 https://github.com/odoo/o-spreadsheet/commit/d214df23 [REF] CF: split side panel into multiple components Task: 3504521 https://github.com/odoo/o-spreadsheet/commit/f954de50 [IMP] PieChart: percentage visualization for tooltip https://github.com/odoo/o-spreadsheet/commit/6bc519e0 [IMP] SidePanel: remove unused css rule https://github.com/odoo/o-spreadsheet/commit/6b9927b6 [MOV] side panel: rename `SidePanelErrors` to `ValidationMessages` https://github.com/odoo/o-spreadsheet/commit/adcda849 [IMP] grid: add specific # of rows at the end of sheet https://github.com/odoo/o-spreadsheet/commit/c8289169 [FIX] sheetview: performance issue for too many rows/cols Task: / https://github.com/odoo/o-spreadsheet/commit/36d3a47e [IMP] spreadsheet: Add Data Validation feature Task: 3422042 https://github.com/odoo/o-spreadsheet/commit/d701460b [REF] filter: create GridCellIcon component Task: 3422042 https://github.com/odoo/o-spreadsheet/commit/953ad1d2 [MOV] error_tooltip: add dedicated test file Task: 3422042 https://github.com/odoo/o-spreadsheet/commit/d61cbee2 [IMP] edition: add CANCEL_EDITION command Task: 3422042 https://github.com/odoo/o-spreadsheet/commit/aad55661 [FIX] Find & Replace: Clear search debounce at unmount Task: / https://github.com/odoo/o-spreadsheet/commit/f91bf8b6 [IMP] SelectionInput: remove useless ternary expression Task: / https://github.com/odoo/o-spreadsheet/commit/a5be6827 [IMP] SelectionInput: add missing release on selectionProcessor Task: / https://github.com/odoo/o-spreadsheet/commit/f94eed58 [FIX] filters: hide sort buttons in readonly mode Task: 3475613 https://github.com/odoo/o-spreadsheet/commit/02436b16 [FIX] locale: string dates in CF aren't (un)localized Task: 3481670 https://github.com/odoo/o-spreadsheet/commit/f7b9b9a5 [FIX] clipboard: cut/paste filter table in another sheet Task: 3498592 https://github.com/odoo/o-spreadsheet/commit/0c8782bd [IMP] EventStream: Observers register only once Task: 3142006 https://github.com/odoo/o-spreadsheet/commit/e008fe2b [FIX] test: undeterministic test in spreadsheet.test.ts https://github.com/odoo/o-spreadsheet/commit/f2cd5abf [REV] find & replace: shorten the debounce on find search Task: 3510813 https://github.com/odoo/o-spreadsheet/commit/549142d4 [FIX] Find&Replace: purge duplicated handler Task: /
Survey creators can now show a question when respondents choose any of several specified answers across different earlier questions. This makes conditional survey flows easier to build and supports more complex branching without duplicating questions.
Original PR description
This PR removes the `triggering_question_id` field and changes the `triggering_answer_id` field from Many2one to Many2many from `survey_question` model, Allowing users to list multiple answers that could trigger a question from multiple questions and multiple answers. for example, there are 3 questions all having 4 options A, B, C, and D. we will have put conditions on Question 3, conditions are if the user selects: Question 1: Answer A or Question 1: Answer C or Question 2: Answer D then, we will display Question 3. taskID-2937533
This update standardizes dropdown, popover, and select-style menus across Odoo so they behave more consistently. Users should see smoother keyboard navigation, more reliable closing behavior, and fewer visual layering issues in areas such as mail, calendars, imports, dashboards, manufacturing, and reporting views.
Original PR description
We currently have too many different implementation of the same concern: an input with a dropdown/popover/select menu that can be customized, display a list of elements, let the user navigate with the keyboard, can be closed with escape, can be closed with an outside click. Also, the current navigation systems does not handle inputs properly. This commit addresses that by doing multiple things: - It tries to improve the Dropdown component with a cleaner props API while keeping its ease of use. - The navigation has been improved to support inputs and better customization. Project task: [3266145](https://www.odoo.com/mail/view?model=project.task&res_id=3266145&access_token=7a09516e-1a2d-4970-a909-0f5099588055) Enterprise PR: https://github.com/odoo/enterprise/pull/42041
Live chat reporting has been enhanced to provide clearer statistics for channels and operators. This helps teams better understand chat activity and operator performance so they can monitor service quality and make staffing decisions.
Original PR description
task-3471332
Time Off reports are easier to use with better default views and filters. Employee reporting now opens in a list view focused on the current year, while type-based reporting now starts with a graph view and clearer filters for time off and allocations.
Original PR description
Before this PR if we go to the Time off and go to reporting in that select the to employee there are graph , calendar, pivot views and there are two default filter active employee , Employee > Type . And After that when we go to to type there are list, pivot view and by default there are 4 filter to the list view of the to type and in list view there is button. Improvements : To Employee : Add the List view and make it default. And make Current year by default. To Type : Add the graph view and make it default. Made changes in the filter add Time off Allocations in that filter. Remove that button and use action method to the record. task-3389174
The Discuss app now responds more naturally to the Escape key. Users can close the channel selector and quickly return focus to the message composer, making conversations faster and easier to navigate by keyboard.
Original PR description
This PR introduce multiple usage of the escape key: - Channel selector can now be closed using the escape key - Using the escape key will focus the composer automatically Task-3456518
This update appears to adjust how canceled projects and tasks are handled or displayed in the Project app. It helps users better identify or manage canceled work, reducing confusion in day-to-day project tracking.
Users can now add people and channel mentions directly in the full chatter composer using @ and #. Mentions are also kept when moving a draft from the small composer to the full composer, making message drafting more consistent and reliable.
Original PR description
Introduce @/#mention function in the full composer of the chatter The mentions should remain consistent between the small and full compose task-3470060 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The survey results page has been redesigned to be cleaner and easier to use, with key survey metrics shown prominently and better controls for filtering, printing, and viewing responses. Users can now hide or show questions, expand all responses when needed, and get printouts that fit better on standard pages.
Original PR description
[IMP] survey: improve results page Purpose ======= Improve the overall look of the page for screen and print media. Display/hide questions, and alternate between pagination and full display of user…
[IMP] survey: improve results page Purpose ======= Improve the overall look of the page for screen and print media. Display/hide questions, and alternate between pagination and full display of user responses. Specifications ============== ### HEADER AND OVERVIEW - remove waste space between Edit Survey button and survey title - remove trophy cup or any icon on the right of the title - put filters on the right of the title - remove background - replace the `Results overview pie chart` by the survey KPI's - add a print button ### QUESTIONS - add a button for each question to toggle their visibility - avoid breaking question into multiple lines, use all space available - change info badges design so they are not mistaken for buttons - remove question type from the info badges ### USER RESPONSES - add a `show all` button per question to display all responses, whitout pager and scrollbar. Users may be able to rollback to pager mode - for each response, push the filter icon to right side of the row - use regular font and color for responses, remove response text from the <a> tag ### PRINT MODE - hide the `webeditor/ back to backend` button - visible questions: display all responses (no pagination or scrollbar) - user responses: hide filter icons - make sure elements like tables are properly cut between pages - resize graphs to ensure they fit into A4 paper page - prevent brand message to disappear or to float over other elements task-3424235 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Bank journals can now choose the newer SEPA Direct Debit format for incoming payment files. This helps businesses stay compatible with upcoming bank and country requirements, including support in Belgium and the Netherlands.
Original PR description
Problem --------- A new version of the SEPA Direct Debit Schema (Pain 008.001.08) is available and will soon be usable in some countries. In Belgium for example, it will be supported by ISABEL soon, and is already published in the Netherlands. Objective --------- Add the new schema and allow the user to select which version to use. Solution --------- 1. In Bank Journal configuration, tab Incoming Payments, add a configuration section where the user can select what version of SEPA Direct Debit he wants to use. Done through a selection field. 2. Implement the SEPA Direct Debit 008.001.08 format and allow the xml export of that schema. task-3440881
This update standardizes dropdown and popover menus used across Odoo, making them more consistent and easier to navigate with the keyboard. Users should see more reliable menu behavior in areas such as accounting reports, consolidation filters, intrastat filters, and pivot views.
Original PR description
We currently have too many different implementation of the same concern: an input with a dropdown/popover/select menu that can be customized, display a list of elements, let the user navigate with the keyboard, can be closed with escape, can be closed with a outside click. Also, the current navigation systems does not handle inputs properly. This commit addresses that by doing multiple things: - It tries to improve the Dropdown component with a cleaner props API while keeping its ease of use. - The navigation has been improved to support inputs and better customization. Project task: [3266145](https://www.odoo.com/mail/view?model=project.task&res_id=3266145&access_token=7a09516e-1a2d-4970-a909-0f5099588055) Community PR: https://github.com/odoo/odoo/pull/119389
Knowledge macros can now work with more eligible HTML fields while keeping existing preferred fields first. The update also better respects field visibility and read-only rules, excludes settings pages from Knowledge access, and simplifies macro error messages.
Original PR description
- Keep the existing priority list for html fields - Allow any other field that is using the `html` widget to be considered (discard others like `mass_mailing_html`). - Evaluate the invisible and readonly modifiers of the `xmlDoc` field instance on top of the modifiers of the Record instance (they are not always consistent). task-3501211
The Twitter social integration was cleaned up after its API migration, removing unused code and improving maintainability. Users also get clearer feed previews, refreshed stream views after adding a stream, and quoted tweets displayed more completely in comment dialogs.
Original PR description
Purpose ======= In c85cf25f58202504aa1366156cce3905369dfe67 , we migrated to the new Twitter API. Because we did the changes in stable, we couldn't clean as we wanted. This commit cleans the social_twitter module and removes unused methods. Task-3492787
Resolved issues and error corrections
This fixes an issue that could prevent uploading multiple files through web requests, including website forms. The change restores expected upload behavior and adds support for a broader request format, reducing errors for users submitting files.
Original PR description
Since [1] an error was thrown when giving multiple files to http.post. This commit reverts changes in the function but the function now also allows to give a FormData instead of pojo. [1]: https://github.com/odoo/odoo/pull/136271
Features or functions removed from Odoo
This change reverts a previously added product information popup for self-ordering and related product fields because the shared ecommerce content was not suitable for POS use. It prevents styling and display problems caused by website-only content being shown in POS or backend screens, while separate follow-up work will create a better POS-specific solution.
Original PR description
Code cleanup and technical improvements
Barcode check-in functionality for events has been moved into the standard Events app available in the community edition. This makes event attendee scanning more broadly available and simplifies the product structure by removing it as a separate enterprise-only component.
Original PR description
event_barcode is moved to community and integrated directly into event module task-3411827
The website editor now makes drop areas more transparent so page content remains easier to read while editing. It also keeps read-only selection outlines visible, preventing layout confusion when selecting areas such as headers or footers.
Original PR description
=== ISSUE 1 === Since the introduction of the new dropzone design, the dropzones weren't transparent enough and the inline content behind them wasn't readable. This PR adapts the layout of dropzones to make the content behind them more readable. === ISSUE 2 === Prior to this PR, read-only handles were hidden, which created a layout issue (eg. the header was no longer highlighted when we clicked on it). This PR adapts read-only handles to make them visible by using a border around the selected element. task-3537616 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This reverts commit 3b9401c35423574b57f1081f9c80bd149d79d76b. It shouldn't have been merged in the first place. The PR was `r-` but it seems like the mergebot bugged and still merged it because there…
This reverts commit 3b9401c35423574b57f1081f9c80bd149d79d76b. It shouldn't have been merged in the first place. The PR was `r-` but it seems like the mergebot bugged and still merged it because there was an occurence of `r+` in the sentence which asked robodoo to `r-`. > robodoo r- just to be sure, since there was a random r+ not [...] Rationale of the revert: - Bad field name: - "ecommerce" in product module - "ecommerce" but used in POS - Arguably very low value to share the field -> This field is used in ecommerce to add info exactly between the price and the name of a product. There is low chance that you want to share that exact information with the POS. - Technically, it couldn't work. What you design in website builder on the product page is related to website assets JS and CSS, which are not loaded neither in the backend and neither in the POS. It was leading to multiple critical issues, mainly: - Losing the whole style of the content (CSS) - Breaking completly the snippets (visually and design wise) (CSS/JS) - Not even show (JS is in charge of showing the content eg) Note that the same issues were already existing in that field in the backend (it's shown in the product form view). The ecommerce team was looking for a solution to make it work, but it's impossible as to work, it would need the website / frontend assets, which can't be loaded in the backend / POS. The cancel of this PR was validated with PO of POS and ecommerce following those explanation, which they weren't aware of. Apart from this revert, further PR will be done to: 1. Remove the field from the product form view (ecommerce app) 2. Create a new field for POS Revert of https://github.com/odoo/odoo/pull/136906 task-3524272