Friday, June 24, 2022
17 changes · master
Enhancements to existing features
The live chat chatbot can now use dedicated welcome steps to start conversations more smoothly. This helps website visitors receive clearer initial guidance and gives businesses a more controlled first interaction in live chat.
Original PR description
*: website_livechat Task-2891987
Live chat conversations can now display a dedicated chatbot name, making automated responses clearer and more personable for website visitors. This helps businesses present a more polished support experience and distinguish bot messages from other live chat interactions.
Original PR description
Task-2891910
The live chat system now uses a dedicated chatbot model and cleaner button state handling, including support for test chatbot data. This makes chatbot behavior easier to manage and helps improve reliability for website live chat experiences.
Original PR description
Task-2891904
Live chat now better tracks the chatbot's last welcome step, helping conversations start more consistently for website visitors. This should make automated chat greetings smoother and reduce confusion when users interact with the chat widget.
Original PR description
Task-2892000
Live chat chatbots now have a clearer model for controlling message timing, including delays between chatbot messages. This improves the visitor chat experience by making automated conversations feel more natural and easier to test and maintain.
Original PR description
Task-2892596
The live chat chatbot code has been reorganized around clearer chatbot and chatbot step data models. This makes chatbot behavior easier to maintain and test, supporting more reliable customer conversations on websites.
Original PR description
*: website_livechat Task-2892283
Survey results now make it easier to see whether answers are correct, incorrect, or skipped, including for date, datetime, and number questions. Scoring fields are only shown when relevant, and missing required scored answers are flagged earlier when saving the question, reducing setup mistakes.
Original PR description
PURPOSE We are able to add scoring for date, datetime and integer question types. The way results are displayed can be improved, that's the main purpose of this PR. Current 1) There is no correct answer displayed on answer page. 2) Input field for point is visible whether score is checked or not. To be 1) Show correct answer For date,datetime and integer in the result page (and also for live survey): 2) Display the input for the score only if score is checked. 3) Trigger the warning "All "Is a scored question = True" and "Question Type: Date" questions need an answer" on the "Save" of the question, not the survey itself. Same way we trigger the missing title:(make it mandatory if score is checked) LINKS PR Task 2276724 I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Salesperson and sales team details are now kept consistent between individual contacts and their linked parent companies. This helps ensure portal users see the right person responsible for handling their process, even when contacts and companies are created or linked in different ways.
Original PR description
PURPOSE The Salesperson and sales team values should be set on the individual partner and the parent company if the parent company is linked with an individual partner. This salesperson will display…
PURPOSE The Salesperson and sales team values should be set on the individual partner and the parent company if the parent company is linked with an individual partner. This salesperson will display on the portal to show who will handle the process. SPECIFICATIONS The Salesperson and sales team are set on contact/partner form view. This salesperson is showing on the portal view(website). This value shows who will handle the process. No contact will show on the portal if the salesperson is not set on individual contact/partner. With this commit, we have done two points. 1) If salesperson and sales team values are set on individual contact/partner, pass these values to a parent company which is created from here(individual contact/partner). 2) If the parent company is manually linked to an individual partner and the salesperson and sales team are not set on an individual, these values are getting from the parent company and set on individual contact/partner. This is the goal of this commit. PR #78696 Task-2636290 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update refreshes the web interface framework used by Odoo, fixing several issues that could cause crashes or incorrect behavior in interface components. It also brings small performance improvements and better support for UI templates, helping make the web experience more stable for users.
Original PR description
Note: this PR is a manual forward port. The original PR are: - in saas-15.3 => https://github.com/odoo/odoo/pull/94249 - in saas-15.4 => https://github.com/odoo/odoo/pull/94407 Release notes:…
Note: this PR is a manual forward port. The original PR are:
- in saas-15.3 => https://github.com/odoo/odoo/pull/94249
- in saas-15.4 => https://github.com/odoo/odoo/pull/94407
Release notes:
https://github.com/odoo/owl/releases/tag/v2.0.0-beta-9
https://github.com/odoo/owl/releases/tag/v2.0.0-beta-10
Details:
Fix: event: no crash when using t-on + modifier on slots/components
Fix: component: fix props comparison code
Fix: component: fix wrong behaviour when using t-on on t-component
Fix: component: props values are own property of props object
Fix: t-out: allow expressions evaluating as number
Fix: compiler: add support for #{...} in string interpolation
Fix: compiler: escape backticks in attributes
Fix: crash when dynamic class have leading space
Imp: slots: add support for t-props on slots props
Imp: tooling: add another d.ts file
Imp: app: small scale perf improvement
Imp: app: add fast path for when component has no prop
Imp: validation: add support for value types
Imp: add support for t-call-context
Ref: compiler: remove useless ; in compiled output
Ref: move some code around
X-original-commit: 3c7e2cb5a2224ff624e0899ca392be8b3828b43a
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-prRecruitment reports were updated to make their labels and data easier to understand, especially by reducing confusion between applicant source and medium. This helps teams interpret hiring performance more accurately and make better decisions from their reports.
Original PR description
This commit aims to improve the recruitment reports clarity, particularly the confusion between source and medium TaskID : 2837445
The appraisal goals interface now makes it easier for employees and managers to monitor progress and deadlines. Completed goals are clearer to identify, and a new visual progress view supports better follow-up during appraisal cycles.
Original PR description
This commit adds: - progression and deadline tracking - a banner on the completed goals form - a graph view on goals progression taskID 2868693
Odoo Social now shows users how close a Twitter post is to the 280-character limit before publishing. Posts that are too long are highlighted and blocked from being saved, reducing failed publishing attempts and user frustration.
Original PR description
Before This PR: While posting a message on Twitter, even though it has some character limit, we can still create a long message which eventually crashes on posting. The 'Retry' button which appears…
Before This PR: While posting a message on Twitter, even though it has some character limit, we can still create a long message which eventually crashes on posting. The 'Retry' button which appears after thus crashing of the post has no use then. So the goal of our commit is to limit the message length and prevent it from sudden posting failure due to character limits issues. After This PR: -Twitter post max length as per its documentation is 280 characters, where standard alphabets and space carry a weight of 1 and as well as emojis and new lines carry a weight of 1. This is now taken into account. -Under the 'message' field we have added a read-only text which indicates the current length out of total characters to be fit in the Tweet we are posting. -If the message length is beyond the max-length we have set, the count the sentence will be highlighted as a warning, -If one tries to post a Tweet with more than the max-length, a user error is threw to limit the characters. Task: https://www.odoo.com/web#id=2517821&menu_id=4720&cids=2&model=project.task&view_type=form
Recruitment reports were updated to make applicant source and medium information easier to understand. This reduces confusion when reviewing hiring performance and helps teams interpret recruitment channels more accurately.
Original PR description
This commit aims to improve the recruitment reports clarity, particularly the confusion between source and medium TaskID : 2837445
This update improves how VoIP connections identify users during sign-in, especially for OnSIP-based phone services. It helps ensure calls connect more reliably when the login name differs from the visible VoIP username, while removing outdated setup code that is no longer needed.
Original PR description
Part of task-2804807.
This update brings the embedded spreadsheet engine up to its latest version. Users benefit from improved chart support, new date-related spreadsheet functions, and fixes that make spreadsheet layouts behave more reliably around headers, hidden rows, columns, and figures.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/f4511b6f [IMP] spreadsheet: export chart stuff https://github.com/odoo/o-spreadsheet/commit/690584fb [FIX] xml: escape…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/f4511b6f [IMP] spreadsheet: export chart stuff https://github.com/odoo/o-spreadsheet/commit/690584fb [FIX] xml: escape chars in regex https://github.com/odoo/o-spreadsheet/commit/be1c78c1 [IMP] Functions: Add several date related functions https://github.com/odoo/o-spreadsheet/commit/cb557f1b [IMP] spreadsheet: export some utilities https://github.com/odoo/o-spreadsheet/commit/b88a5fac [FIX] Figure container: Crop figures to avoid overlap with headers https://github.com/odoo/o-spreadsheet/commit/9e12eaee [FIX] SheetPlugin: clear hidden cols/rows references in plugin https://github.com/odoo/o-spreadsheet/commit/ad019c5a [REF] Header Sizes: rename internal variable https://github.com/odoo/o-spreadsheet/commit/521c9b04 [REF] viewport: merge viewport and snapped viewport https://github.com/odoo/o-spreadsheet/commit/aa18b44e [FIX] header sizes: some small fixes https://github.com/odoo/o-spreadsheet/commit/8e11dd74 [REF] sheet: move header visibility out of sheet plugin https://github.com/odoo/o-spreadsheet/commit/108d337f [REF] sheet: put header size in its own plugin
Odoo Studio now lets users choose the field used to consolidate Gantt views when setting up consolidated planning views. This makes it easier for businesses to build meaningful workload or capacity summaries directly in Studio, while avoiding unsuitable fields like record IDs.
Original PR description
TASK:- https://www.odoo.com/web#view_type=form&model=project.task&id=40680&active_id=40680 PAD:- https://pad.odoo.com/p/r.4a8172a3a7c3fa59ebefc2fb6c649ab5 When a type of gantt view is 'consolidate', we need to set an extra attribute named 'consolidation'. Using studio, we were able to set the type of a gantt view, but could not set consolidation attribute in case of consolidated gantt view. This commit adds an option to choose the consolidation attribute from supported field types (integer, float or monetary). ID filed is excluded from the supported fields as it doesn't make sense to see a gantt consolidated by ID. Task: #40680
Internal users who create helpdesk tickets will now receive email links that take them to the backend when they have the right access. This helps staff reach the fuller ticket view faster, instead of landing on a limited customer-facing page.
Original PR description
Purpose ======= When an internal user creates a helpdesk ticket, they will get a link by email to the front end which does not contain a lot of information. If the user is part of the group_helpdesk_user group Task-2680414