Friday, January 14, 2022
9 changes · master
Enhancements to existing features
The search bar now removes accidental spaces before and after entered keywords. This helps users get the expected results when typing or pasting text with extra whitespace, reducing failed searches caused by simple formatting mistakes.
Original PR description
When the search field is used to query an element, the value is trimmed to remove unnecessary spaces before and after the actual keywords. This eliminates the annoyance of a search having no result because of a space that was left (for example when copy- pasting some text). A test has been added to check if a value has been trimmed when the text input contains spaces. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The command palette was updated internally to access part of its screen layout in a more reliable way. This helps keep the web interface compatible with the newer Owl 2 framework, reducing future maintenance risk without changing user-facing behavior.
Original PR description
The commit adapts the CommandPalette to use a t-ref to a node
in the template instead of a this.el.querySelector("...") in the
component to query an element. This will improve the
compatibility with Owl 2.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update changes how certain web interface text is rendered so it is treated as regular text rather than raw content. This helps reduce unnecessary risk while keeping the user experience unchanged.
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
This update adjusts internal mail and discussion interface components to prepare them for a future OWL 2 technology upgrade. It should not change day-to-day user behavior, but helps keep the messaging area easier to maintain and modernize.
Original PR description
In preparation to use OWL 2 in discuss code. Task-2694206
The base linting configuration was adjusted so local development tools work more reliably without extra setup. This reduces friction for contributors and keeps broader project checks better aligned with dedicated CI configuration.
Original PR description
The usage of `select=RST` apparently broke all local flake8 uses (which might be implicit e.g. used for linting in the simpler editors). Always excluding "addons" probably causes a similar problem. Remove the exclusion of "addons", and use "extend-select" for the selection of RST errors. This should play better with local configuration, or the lack of configuration (thus flake8 defaults). This means the exclusion of addons and the "blanking" of the default errors selection will have to be done in the CI configuration, but that probably makes sense.
Mass mailing administrators can now disable next-day mailing reports from settings or directly from the report email. This reduces unwanted report emails while keeping reports enabled by default for teams that rely on them.
Original PR description
Purpose ======= Allow users with enough access rights to disable next-day report on mass mailing lists. The option has been added in the mass mailing settings and is enabled by default. Mass mailing reports can also be disabled with a "Turn off mailing reports" button in the report email itself. Reports are enabled and disabled for all Responsible. Task-2692211
This update makes sales orders, quotation templates, and quotation builder data update automatically and consistently instead of relying on manual screen-triggered changes. It improves consistency between backend and frontend behavior, especially for multi-company setups, while reducing unnecessary processing during installation.
Original PR description
Convert most remaining onchanges/defaults/... to computed fields and compute methods. - [x] Check perf of sale_mngmt/sale_quot_builder install on existing db with sale (pre-create columns to avoid useless updates/recomputations) ? - [x] Verify multi-comp behavior (make sure company_id is correctly computed on order lines & options, s.t. the dynamic domains work as expected). Task ID - 2716304 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Survey results pages are easier to read and filter, with clearer completion/pass/fail filters and visible counts before filters are applied. Scores, correct answers, unanswered questions, and date/time responses are presented more clearly, helping users interpret survey performance faster.
Original PR description
PURPOSE Various improvements of the results' statistics were required, mainly regarding * the filtering features that were not clear and impractical * the way answer scores was reported * the…
PURPOSE Various improvements of the results' statistics were required, mainly regarding * the filtering features that were not clear and impractical * the way answer scores was reported * the vertical space taken by questions never answered Among other smaller changes, the layout of `datetime`-answers questions is harmonized with the other answer-types (grouped by value), considering that the "time" part is important and that the "seconds" part bof that time would only be changed if it is relevant to the question. SPECIFICATIONS **Filters** It is now more convenient to filter surveys based on: - Whether they are fully completed - Whether they are passed - Whether they are failed (last 2 are mutually exclusive, and only available for scored tests) A badge is added to show the number of surveys that match each filter option if chosen. Note that this simple implementation does not allow to show the number of surveys which would be displayed if the filter was removed, or replaced, so the badges are not shown once a filter is selected. The question/answer filters can now be removed individually. The i.fa-filter elements used to activate them are now always visible, and are only available for answers that have been selected at least once. **Scoring** Scores are added in tables next to the answers instead of as additional lines below the question caption. Right answers are now marked in the Graph and Data tabs instead of being simply listed under the question. **Unanswered questions** To make this special case more clear to the user, a discrete alert is added below the question. The Graph and Table tabs are removed in this case, as they contain no information. For Multiple choice and Matrix questions, the Table tab stays visible to show the possible answers available. *Misc* To follow common representation, numbers which are equal to integer values will show as integers in answers and scores (e.g., 30.0 will show as 30), using a sub-template. Distinguishing the questions and results from the previous/next ones was difficult, hence the added margins and discrete lines. Similarly to other fields, datetime results now display one line per answer value, with its occurrence. Stylesheets are cleaned up. LINKS Task-2618399 See odoo/upgrade#3168
Helpdesk SLA reports now show clearer business metrics such as failed tickets, success and failure rates, successful tickets, and tickets in progress. Default reporting focuses on the last 30 days by Helpdesk Team and SLA, making it easier to quickly understand service performance and identify problem areas.
Original PR description
The current SLA status analysis report is hard to understand and doesn't provide much added value. As such, this commit focuses on providing more relevant information to the user. This commit will: -…
The current SLA status analysis report is hard to understand and doesn't provide much added value.
As such, this commit focuses on providing more relevant information to the user.
This commit will:
- Remove the 'SLA Status Failed' measure
- Rename 'ticket failed' into 'Failed Tickets'. This measure will represent the number of tickets
with at least one SLA failed
- Add a 'Success Rate' measure that will represent the % of tickets closed without failing the SLA
vs. the total number of tickets
- Add a 'Failure Rate' measure that will represent the % of tickets closed and having failed the SLA
vs. the total number of tickets
- Add a 'Successful Tickets' measure that will represent the number of tickets closed without failing the SLA
- Add a 'Tickets in Progress' measure that will represent the number of tickets with this SLA in progress
- Change the 'day to reach SLA' measure to 'Hours to reach SLA'
- Remove the 'open time (hours)' measure
- Rename 'time to first assignment (hours)' into 'Hours to Assign'
- Rename the 'Time to close (hours)' measure into 'Hours to Close'
- Format the values from the measures expressing hours as 00:00 instead of 0
- By default:
- The filter will be 'last 30 days'
- The report will be grouped by Helpdesk Team > SLA
- The measures will be: 'tickets failed' + 'failure rate'
task-2500895