Monday, June 13, 2022
39 changes · master
Enhancements to existing features
This update improves the website live chat experience by making chatbot and live chat components load more reliably for public visitors. It also fixes frontend issues that could cause repeated errors or crashes when assets or user localization data are missing.
Original PR description
Task-2879078
This update introduces a clearer live chat button view and configurable button text across the live chat experience. It helps businesses present chat entry points more consistently on websites and improves the foundation for live chat behavior across related apps.
Original PR description
*: website_livechat Task-2878976
This update improves the website live chat experience by introducing a dedicated live chat button view and customizable input placeholder behavior. It helps make chat interactions clearer for visitors while supporting a more consistent setup across website and live chat components.
Original PR description
Task-2878710
This update improves how the live chat button and visitor display name are handled, helping website conversations start more smoothly and consistently. It also aligns related chat, website, survey, and web components so the public chat experience is easier to maintain and more reliable.
Original PR description
Task-2878726
Project portal pages now use clearer labels for time spent and show more related business information, including linked sales orders, quotations, tickets, invoices, and contact emails. This makes it easier for customers and internal users to understand task context, billing status, and any overrun on remaining sales order hours.
Original PR description
The purpose of this commit, is to make improvements in Project. In this commit, following changes are made: -rename 'Duration' to Hours/Days Spent -rename hours/days to Hours/Days Spent -add links to Sales Order, Quotation, Ticket and Invoices linked the task in left panel -indicate email of the assignee -indicate email of the partner -indicate 'Draft Invoice' instead of '/' for invoices -display 'remaning hours on SO' value in red if value is less than 0 task-2743512 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Project update screens now show tracked time in an easier-to-read hours-and-minutes format. When multiple sales order items use the same product, their prices are also shown so users can tell them apart more easily.
Original PR description
With this improvement, * in the Project Updates kanban/tree side pannel : > Hours are displayed 'HH:mm Hours' * in the Project Updates form description : > idem > Sales Order Items with the same products also display their price to differentiate them. task-2841685 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 the messaging framework available to the website live chat experience, laying groundwork for a future modernization of live chat behavior and interface. It also includes reliability fixes that prevent repeated service startup and avoid error loops when website assets are missing.
Original PR description
This commit make messaging service available in the frontend and in the livechat external lib bundle. This is preparation to refactoring JS livechat to use models and OWL. *: bus, mail, survey, web, website_livechat Task-2870899
The mail chat window header no longer includes controls for shifting a chat left or right. This simplifies the chat interface and reduces options that were likely unnecessary or confusing for users.
Original PR description
Task-2882557
The Mail app now has a clearer structure for managing conversation channels and their members. This supports better participant lists and lays the groundwork for more reliable messaging experiences.
The spreadsheet document action label was adjusted from “Save as Template” to “Save as template” for more consistent wording. This is a small user interface polish that helps keep menu and wizard text aligned across the Documents spreadsheet experience.
Original PR description
`Save as Template` => `Save as template` task 2824232
Pivot tables inserted into Documents spreadsheets now keep the sorting chosen in the pivot view. This makes spreadsheet reports more consistent and useful, especially when using position-based pivot formulas.
Field Service tasks are easier to manage with clearer customer addresses, planned dates, linked helpdesk tickets, and improved sorting. Customers and staff can also access worksheet details, signatures, printing, downloads, and time and material information more directly through the portal and task views.
Original PR description
*-= helpdesk_fsm,industry_fsm_forecast,industry_fsm_report, industry_fsm_sale,industry_fsm_sale_report,project_enterprise The purpose of this commit, is to make improvements in Field Services. In this commit, following changes are made: -add link to ticket associated with the task -indicate the address of partner on fsm tasks -remove 'view worksheet' button add download/print and sign buttons in fsm task form view -add 'planned date' field below project -add content of the worksheet with signature of the partner -add shortcut to this section in the left panel -'allow_forecast' is set to false by default for fsm tasks -add 'Time & Material' from the worksheet report in fsm task form view -add sort by 'planned date' in tasks tree view Related PR: https://github.com/odoo/odoo/pull/86422 task-2743512
Planning shift details are now clearer for employees, with dates, durations, and allocation percentages shown in a single, localized format. Open shifts and related sales order information are easier to scan and act on, with clearer labels, better layout, and row highlighting.
Original PR description
front-end popover - rename 'start date' into 'date' - remove the end date and allocated hours fields, instead indicate 2021-12-21 07 AM -> 2021-12-21 11:00 AM (2h) (50%) as the date - the allocated time % should only be visible if different from 100% - the date should respect the format configured on the language of the employee - move the SOL field below the task - indicate the SO nb in the SOL front-end open shifts list - transform the date into 2021-12-21 07 AM -> 2021-12-21 11:00 AM (2h) (50%) - the allocated time % should only be visible if different from 100% - move the SOL field on the right of the task - rename 'assign me this shift' into 'assign to me' - indicate the SO nb in the SOL - highlight the rows on hover task-2741623
Generated timesheets from planning now use each employee's contract working calendar, so hours match schedule changes such as moving from full-time to part-time mid-month. This improves billing and reporting accuracy, including cases involving archived employees assigned through planning roles.
Original PR description
The purpose of the commit is to take the contract working calendars into account for the auto-generated timesheets of the planning. For Ex: An employee's working time changes during month A (from a full time to a half time (every morning). A the end of month A, the manager generates the timesheet for the past month. When generating the timesheets, - all the slots with a date_end prior to the working time change should take 8h per day. - If there is a slot with a start_date prior to the working time change and an end_date after the working time change, it should take 8h before the working time change and 4 after. - All the slots having a start_date after the working time change should take 4 hours. task-2793011
Project Updates now show hours in a clearer hours-and-minutes format across list, kanban, and form views. Sales order items with the same product also show pricing details, making it easier to tell similar items apart.
Original PR description
With this improvement,
* in the Project Updates kanban/tree side pannel :
> Hours are displayed 'HH:mm Hours'
* in the Project Updates form description :
> idem
> Sales Order Items with the same products also display their
price to differentiate them.
Related PR: https://github.com/odoo/odoo/pull/90624
task-2841685Users now get a dedicated confirmation step when rejecting or changing batch payments during bank reconciliation. This helps prevent accidental changes and makes batch payment handling clearer in accounting workflows.
Original PR description
…on wizard Allow the user to confirm the manipulations he mades in the bank reconciliation widget regarding the batch payments. task: 2856147
Resolved issues and error corrections
Event organizers can now search registration records by the answers attendees selected or typed in event questions. This makes it easier to group, find, and organize attendees based on their responses.
Original PR description
Since: a0092d0011ec62de62e46dfa57cd16ff83bd7201
Users can see attendees' selected answers in the registrations list view using
an optional field ("registration_answer_ids").
However, searching on this field is currently not correctly supported as the
"event.registration.answer" model does not implement it (no "_rec_name" and no
"_rec_names_search").
This commit adds a "_rec_names_search" attribute to allow users to search on
both "value_answer_id" and "value_text_box" fields.
This makes it easy to search for all attendees that have filled in a specific
answer, allowing a better organization of the event based on question results.
Task-2868203Miscellaneous changes
Since this commit https://github.com/odoo/odoo/commit/06a8c5264eb6e87c29ad1d23a14e12dd45aa281c the function sleep was not available when executing python code in safe_eval opw:2858779 Forward-Port-Of: odoo/odoo#93045
Original PR description
Since this commit https://github.com/odoo/odoo/commit/06a8c5264eb6e87c29ad1d23a14e12dd45aa281c the function sleep was not available when executing python code in safe_eval opw:2858779 Forward-Port-Of: odoo/odoo#93045
Documents spreadsheets now use a dedicated loading error instead of the text "Loading..." while data is still being fetched. This prevents unfinished data from being treated as a real formula value and improves reliability when fetches fail or are retried.
Original PR description
[REF] documents_spreadsheet: throw custom loading error Currently, formulas which are loading some date return the string "Loading..." This can lead to weird situations where the string is the input to another formula which understands it as a valid input and could potentially be used as an unexpected RPC argument. Task 2880112 Co-authored-by: Rémi Rahir <rar@odoo.com>
Description of the issue/feature this PR addresses: The template of the standard emoji picker has recently been updated. This commit will update the emoji picker of Knowledge to make the custom components compatible with the new standard templates. Current behavior before PR: When the user opens the emoji picker, the system shows a traceback because some template variables are not defined on the custom emoji component of Knowledge. ``` Error: Invalid loop expression prepareList@h
Original PR description
Description of the issue/feature this PR addresses: The template of the standard emoji picker has recently been updated. This commit will update the emoji picker of Knowledge to make the custom…
Description of the issue/feature this PR addresses:
The template of the standard emoji picker has recently been updated. This commit will update the emoji picker of Knowledge to make the custom components compatible with the new standard templates.
Current behavior before PR:
When the user opens the emoji picker, the system shows a traceback because some template variables are not defined on the custom emoji component of Knowledge.
```
Error: Invalid loop expression
prepareList@https://16138668-master-all.runbot71.odoo.com/web/assets/1694-d28bc19/web.assets_common.min.js:1230:12
template@https://16138668-master-all.runbot71.odoo.com/web/assets/1694-d28bc19/web.assets_common.min.js line 1583 > Function:19:67
_render@https://16138668-master-all.runbot71.odoo.com/web/assets/1694-d28bc19/web.assets_common.min.js:1092:96
render@https://16138668-master-all.runbot71.odoo.com/web/assets/1694-d28bc19/web.assets_common.min.js:1091:6
initiateRender@https://16138668-master-all.runbot71.odoo.com/web/assets/1694-d28bc19/web.assets_common.min.js:1132:47
```
Desired behavior after PR is merged:
The emoji picker works properly.
task-2871883
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#92863There was an issue when canceling the move of an article from one section to another: a previous move which was not canceled could be undone when it should not have been. Impacted versions: * 15.4+ Steps to reproduce: 1. Have one article (A) in the "workspace" section and one article (B) in the "private" section 2. move (A) into "private", validate the move in the dialog 3. move (B) into "workspace", discard the move in the dialog Current behavior: * (A) is
Original PR description
There was an issue when canceling the move of an article from one section to another: a previous move which was not canceled could be undone when it should not have been. Impacted versions: * 15.4+…
There was an issue when canceling the move of an article from one section to
another: a previous move which was not canceled could be undone when it should
not have been.
Impacted versions:
* 15.4+
Steps to reproduce:
1. Have one article (A) in the "workspace" section and one article (B) in the
"private" section
2. move (A) into "private", validate the move in the dialog
3. move (B) into "workspace", discard the move in the dialog
Current behavior:
* (A) is displayed as if it is currently in "workspace" but it is in fact
still in "private"
Expected behavior:
* (A) and (B) should be displayed in the "private" section
This commit fixes the problem by manually replacing the article whose move was
discarded (B) at its previous position while triggering a "change" event instead
of a "cancel" event.
The bug is caused by an incorrect implementation of the "cancel" handler in
`jquery.mjs.nestedSortable` library. Since this library uses jQuery and it is
discontinued, we should consider to reimplement the feature internally in the
future.
This commit also synchronizes data-attr attributes (parent-id and section) with
the hidden value data('attr') from jQuery for consistency.
Task-2877766
Forward-Port-Of: odoo/odoo#93003Patching the window object is not robust and can lead to errors. In order to make patchUiSize more robust, patching of window have been replaced by a patch of the uiService. Forward-Port-Of: odoo/odoo#93347
Original PR description
Patching the window object is not robust and can lead to errors. In order to make patchUiSize more robust, patching of window have been replaced by a patch of the uiService. Forward-Port-Of: odoo/odoo#93347
Fine tuning of da8def8e410de68256ba4ab09ebf7a8b699355ac 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 Forward-Port-Of: odoo/odoo#93211
Original PR description
Fine tuning of da8def8e410de68256ba4ab09ebf7a8b699355ac 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 Forward-Port-Of: odoo/odoo#93211
Trigger up o-message-posted was inadvertently removed in https://github.com/odoo/odoo/pull/76718 task-2880739 Forward-Port-Of: odoo/odoo#93357 Forward-Port-Of: odoo/odoo#93282
Original PR description
Trigger up o-message-posted was inadvertently removed in https://github.com/odoo/odoo/pull/76718 task-2880739 Forward-Port-Of: odoo/odoo#93357 Forward-Port-Of: odoo/odoo#93282
no need to make rounding during computing qty_available STEPS (see the test): * create product with uom dozens * create product with uom units * create bom kit to convert one to another * set qty on hand to 1 for product dozens * check qty for product units opw-2849397 All ready issue is fixed in v14 https://github.com/odoo/odoo/pull/76145 Forward-Port-Of: odoo/odoo#92744
Original PR description
no need to make rounding during computing qty_available STEPS (see the test): * create product with uom dozens * create product with uom units * create bom kit to convert one to another * set qty on hand to 1 for product dozens * check qty for product units opw-2849397 All ready issue is fixed in v14 https://github.com/odoo/odoo/pull/76145 Forward-Port-Of: odoo/odoo#92744
Forward-Port-Of: odoo/odoo#93307
Original PR description
Forward-Port-Of: odoo/odoo#93307
currently there were no changes in the 'next occurrences' dates while clicking checkbox of the particular weekdays. so in this commit we have called onchange explicitly. task id-2823432 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 Forward-Port-Of: odoo/odoo#89846
Original PR description
currently there were no changes in the 'next occurrences' dates while clicking checkbox of the particular weekdays. so in this commit we have called onchange explicitly. task id-2823432 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 Forward-Port-Of: odoo/odoo#89846
STEPS: * switch to serbian language * start chat with a user who is out of office * refresh page BEFORE: Incorrect locale information provided AFTER: no errors Similar change for web module in v15: https://github.com/odoo/odoo/commit/1bb9cb89c8b5b5c55299afd3c53df14c3aea5ee7 opw-2859402 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
Original PR description
STEPS: * switch to serbian language * start chat with a user who is out of office * refresh page BEFORE: Incorrect locale information provided AFTER: no errors Similar change for web module in v15: https://github.com/odoo/odoo/commit/1bb9cb89c8b5b5c55299afd3c53df14c3aea5ee7 opw-2859402 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 Forward-Port-Of: odoo/odoo#93200
Update to latest runbot state, at least for tests known to be deterministic. Notably mail tests are lower than before, probably due to odoo/odoo#73271 Forward-Port-Of: odoo/odoo#93398
Original PR description
Update to latest runbot state, at least for tests known to be deterministic. Notably mail tests are lower than before, probably due to odoo/odoo#73271 Forward-Port-Of: odoo/odoo#93398
Since #75862, the group "Upsell & Cross Sell" was shown in the "Sales" tab of the product views, even if empty (its content is only defined in modules sale_product_configurator & website_sale). This commit makes sure that the group is invisible while it has no content. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#93442 Forward-Port-Of: odoo/odoo#93339
Original PR description
Since #75862, the group "Upsell & Cross Sell" was shown in the "Sales" tab of the product views, even if empty (its content is only defined in modules sale_product_configurator & website_sale). This commit makes sure that the group is invisible while it has no content. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#93442 Forward-Port-Of: odoo/odoo#93339
Before this commit the feature to auto-reload on attachment changed only worked through composer or attachment box, now also works with "upload file" activity. Forward-Port-Of: odoo/odoo#93361 Forward-Port-Of: odoo/odoo#93288
Original PR description
Before this commit the feature to auto-reload on attachment changed only worked through composer or attachment box, now also works with "upload file" activity. Forward-Port-Of: odoo/odoo#93361 Forward-Port-Of: odoo/odoo#93288
Since #79093, the onchange updating taxes according to fpos was replaced by a compute, but the dependency on the order fpos was not kept to avoid full recomputation of taxes (& potentially other things) when SO fields are modified. Nevertheless, it makes sense in some flows to update the fpos after creation of SOlines, and to want the taxes to be updated accordingly. To provide this ability, a new button is added, following the existing logic to update the prices & discounts when the
Original PR description
Since #79093, the onchange updating taxes according to fpos was replaced by a compute, but the dependency on the order fpos was not kept to avoid full recomputation of taxes (& potentially other things) when SO fields are modified. Nevertheless, it makes sense in some flows to update the fpos after creation of SOlines, and to want the taxes to be updated accordingly. To provide this ability, a new button is added, following the existing logic to update the prices & discounts when the pricelist is changed. Task - 2865882 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#93420 Forward-Port-Of: odoo/odoo#92365
Inner `afterNextRender` could potentially resolve/reject after the test has already ended due to missing await (arrow function with bracket is sync). This will prevent tests from overlapping each other. Forward-Port-Of: odoo/odoo#93365 Forward-Port-Of: odoo/odoo#93345
Original PR description
Inner `afterNextRender` could potentially resolve/reject after the test has already ended due to missing await (arrow function with bracket is sync). This will prevent tests from overlapping each other. Forward-Port-Of: odoo/odoo#93365 Forward-Port-Of: odoo/odoo#93345
After the refactor performed on 3fea5b213 to start using OWL, a lot of ARIA attributes were lost. ARIA attributes are required to ensure good compatibility with asistive technologies and keyboard users. This commit reintroduces such attributes, which include: - `aria-label`: used for elements with title but no text - `role`: mainly used for elements that behaves as buttons or links - `aria-expanded`: used on buttons that toggle menus or content, e.g. button to open attachments or f
Original PR description
After the refactor performed on 3fea5b213 to start using OWL, a lot of ARIA attributes were lost. ARIA attributes are required to ensure good compatibility with asistive technologies and keyboard users. This commit reintroduces such attributes, which include: - `aria-label`: used for elements with title but no text - `role`: mainly used for elements that behaves as buttons or links - `aria-expanded`: used on buttons that toggle menus or content, e.g. button to open attachments or followers - And another ones like `aria-pressed`, `tabindex`, etc -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#93299 Forward-Port-Of: odoo/odoo#86324
Create a standard tax that is included in the product price. Add that tax to a product and the down payment product. Create a sales order (i.e. 1 line, 115$ total, 15% tax incl). Create a percentage down payment invoice, i.e. 50%. The downpayment amount will be 50% of the untaxed amount, i.e. 100$ @ 50% = 50$ with tax already included, so actually lower than 50% Forward-Port-Of: https://github.com/odoo/odoo/pull/65275 opw-2858506 Forward-Port-Of: odoo/odoo#93408
Original PR description
Create a standard tax that is included in the product price. Add that tax to a product and the down payment product. Create a sales order (i.e. 1 line, 115$ total, 15% tax incl). Create a percentage down payment invoice, i.e. 50%. The downpayment amount will be 50% of the untaxed amount, i.e. 100$ @ 50% = 50$ with tax already included, so actually lower than 50% Forward-Port-Of: https://github.com/odoo/odoo/pull/65275 opw-2858506 Forward-Port-Of: odoo/odoo#93408
Whilst introducing the fix to allow for some rudimentary processing of supplementary units f1d4b31 , in formatting a section of the p/st codes was not included. This commit adds them in the place where they belong in the dictionary. task-id: 2853030 Forward-Port-Of: odoo/enterprise#28292
Original PR description
Whilst introducing the fix to allow for some rudimentary processing of supplementary units f1d4b31 , in formatting a section of the p/st codes was not included. This commit adds them in the place where they belong in the dictionary. task-id: 2853030 Forward-Port-Of: odoo/enterprise#28292
Update to latest runbot state, at least for tests known to be deterministic. Forward-Port-Of: odoo/enterprise#28294
Original PR description
Update to latest runbot state, at least for tests known to be deterministic. Forward-Port-Of: odoo/enterprise#28294
In certain conditions, the pivot data were not correctly fetched from the `pivotModel`when loading the `PivotDialog`to re-insert a cell. Specifically, the issue arises when at least one groupBy is a relational field which is not set for some records. (e.g. user_id not set on res.partner records). The problem was that when parsing the groupBy value in `parsePivotFormulaFieldValue`, the code only worked if the input groupValue was always a string. This commit ensures that `parsePivot
Original PR description
In certain conditions, the pivot data were not correctly fetched from the `pivotModel`when loading the `PivotDialog`to re-insert a cell. Specifically, the issue arises when at least one groupBy is a relational field which is not set for some records. (e.g. user_id not set on res.partner records). The problem was that when parsing the groupBy value in `parsePivotFormulaFieldValue`, the code only worked if the input groupValue was always a string. This commit ensures that `parsePivotFormulaFieldValue` properly handles all types of inputs, therefore fixing the aforementionned symptom. Task 2870790 Forward-Port-Of: odoo/enterprise#28033
…d on the bank reco widget Forward-Port-Of: odoo/enterprise#28252
Original PR description
…d on the bank reco widget Forward-Port-Of: odoo/enterprise#28252