Thursday, April 6, 2023
11 changes · master
Enhancements to existing features
The installation documentation now includes guidance for configuring system language settings. This helps prevent setup failures and warning messages caused by misconfigured server locales, making deployments more reliable.
Original PR description
Fix the following errors:
- `DataError: new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII) HINT: Use the same encoding as in the template database, or use template0 as template.`
- https://www.odoo.com/es_ES/forum/ayuda-1/question/dataerror-new-encoding-utf8-is-incompatible-with-the-encoding-of-the-template-database-sql-ascii-52124
- `/werkzeug/filesystem.py:63: BrokenFilesystemWarning: Detected a misconfigured UNIX filesystem: Will use UTF-8 as filesystem encoding instead of 'ANSI_X3.4-1968'`
- https://stackoverflow.com/questions/34515331/werkzeug-raises-brokenfilesystemwarningThis update adds automated checks for the shared tag display component and removes configuration that was no longer actually used. It helps keep tag displays consistent across areas like Project and the general web interface while reducing maintenance risk.
Original PR description
*: project This commit adds test to this component and removes unused props. Since commit (1), it is now considered as a core component. Those props have been removed from the props declaration, to better match the real usage of the component. Since the className props was not present: - The o_kanban_tag class given in theory were not set in practice. The rules corresponding to that class were already adapted to fix the display of tags in the kanban view. It was possible to get rid of the references to the o_kanban_tag class. - The o_field_property_tag_readonly class was also missing, and the logic to prevent the click on tags was duplicated in the onTagClick function. This makes the class useless. I removed mentions to this classname. (1): 129fa3f150fe8b084f054036da7f399855d3ef0c
Odoo can now handle requests to place empty values first or last when sorting records. This makes list ordering more predictable, especially for descending sorts and related records where empty values previously could appear in confusing positions.
Original PR description
Recent Odoo versions require modern postgres (e.g. use of jsonb), the `NULLS {FIRST | LAST}` clause was added in 8.3 so should be well supported. While Odoo's use of nulls is not always consistent,…
Recent Odoo versions require modern postgres (e.g. use of jsonb), the `NULLS {FIRST | LAST}` clause was added in 8.3 so should be well supported.
While Odoo's use of nulls is not always consistent, the NULLS ordering clauses can be quite useful especially when sorting `DESC`: `NULLS FIRST` and `NULLS LAST` are literal positions so they put nulls at that location regardless of sort order whereas the default Postgres ordering is to consider nulls larger than every other value so they appear first when sorting DESC, which is often undesirable (putting nulls first when sorting ASC can also be useful to fill records).
Update `_generate_order_by_inner` to correctly process `NULLS` clauses:
- Use `regex_order` to ensure we parse orderings correctly and consistently, also update `regex_order` to use named groups to make the relevant bits clearer (and VERBOSE for readability).
- Given `a_id DESC` and `_fields[a_id].relation._order = 'xxx NULLS LAST'`, reversing the clause should order by `xxx DESC NULLS FIRST` to correctly flip the original as `NULLS` clauses are not relative to the sorting order (they put the `NULL`-valued records at the specified location regardless). Therefore apply `reverse_direction` to `NULLS`.
- Manually expand `NULLS` clauses on m2o fields: propagating the clause through the join would yield unexpected and illogical results when mixing NULL m2o fields and non-NULL m2o fields with NULL `_order` fields (as they would get mixed rather than clearly layered / separated).
However because SQL booleans are ordered the usual way (`true > false`) the `NULLS` clause is fundamentally equivalent to sorting on the field being NULL (if `NULLS LAST`) or not (if `NULLS FIRST`). So we can prepend the expanded m2o's ordering with such a clause to get the correct behavior.
Replaces #116464
Supersedes #116664Small icon menus in the Odoo navigation bar are now easier to use because they no longer open automatically while moving across nearby menus. This reduces accidental menu openings and makes navigation smoother, especially around debug, messaging, and activity menus.
Original PR description
The first commit removes the manualOnly prop on the Dropdown component and all its related code because it seems unused. The second commit adds a new prop to the Dropdown component: autoOpen. It is true by default and follows the current behavior of all current dropdowns (automatically open the dropdown when it is hovered and a sibling is already opened) when set to true and disable this feature for the dropdown when set to false. The commit also applies this new property and set it to false on all dropdowns that are present by default in the enterprise navbar to facilitate navigation with those that are too small (debug, messaging and activity) opw-3259473
Call participant cards now show a clickable error indicator that lets users retry playback when browser media restrictions interrupt audio or video. This makes online calls easier to recover without leaving or restarting the call.
Original PR description
This commit improves the overlay icon that appears on call participant cards when an error in the media players occur. The icon is now clickable, which restarts an attempt to play all the `HTMLMediaElement`s of the call as a recoverable error can occur when the browser does not allow `HTMLMediaElement`s being played outside a user interaction. other related changes: * removing the `pointer-event:none` from the overlay as it was preventing hover events, and the title tooltip from appearing. * removing the try/catch around the `srcObject` assignment, as it should only crash on old browsers without support for `srcObject` for which the support of using the alternative (`URL.createObjectUrl` with `src`) is being dropped.
Project profitability now includes manually added analytic accounting lines when they clearly belong to a single project, giving managers a more complete view of costs and revenues. Portal pages also show the specific task, ticket, or project name, and task dependency notifications are clearer for users.
Original PR description
This commit purpose is - to add the all the user adds manually to the panel of project profitability if there is only project linked to the analytic account. - to remove the stage tracking for task dependencies, and instead log a note to warn the user when all the blocking tasks are closed. If one of those task is reopened, message is sent to warn that the task is blocked again - to display the name of the current task/ticket/project on the portal page instead of the generic My tasks/etc - to update the name of notification sub-types task/project dependcy task-2960753 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
Helpdesk portal ticket pages now use the current ticket name instead of a generic “My Tickets” page title, making it easier for customers to understand where they are. Related field service sales profitability tests were updated to stay aligned with recent underlying changes.
Original PR description
This commit purpose is to - update the test of test_project_profitabilty in accordance to the changes made in the communty part of this task. - change the generic My tickets page name of the portal into the name of the current ticket task-2960753
Odoo Studio now shows a helpful message in the sidebar when a separator element is selected. This avoids an empty properties panel and makes the editing experience clearer for users configuring views.
Original PR description
This commit simply provides some feedback in the properties tab of the sidebar when a separator element is selected instead of displaying nothing. opw-3259505
Odoo’s document scanning has been upgraded to a newer OCR version for invoices, expenses, and recruitment documents. This improves compatibility with the latest extraction service and adjusts how extracted results are handled, including cases where suggested values may be missing.
Original PR description
Upgrade to the latest OCR version (app: 102, exp: 132, inv: 122). With this version, we do not send the `global_taxes` nor the `global_taxes_amount` anymore. `words` in the response were replaced by the more suitable `candidates`. It is now possible to not have `candidates` in the response, and it is also possible to have no `selected_value`.
The Helpdesk overview page now gives clearer performance context with an updated success rate explanation and color-coded performance indicators against daily targets. Urgent ticket actions also open with the urgent filter applied by default, helping teams focus on priority work faster.
Original PR description
In this PR change following UI changes in helpdesk overview page: - change the 'success rate' tooltip to - "Percentage of tickets whose SLAs have successfully been reached on time over the total number of tickets closed within the past 7 days." - 'Today' and 'Avg Last 7 days' my performance buttons in btn-success if the value is >= to their daily target else btn-warning. - set the 'urgent' filter by default in team kanban card urgent action task-3186583
Portal users can now see how many shared documents are linked to a project task even when the shared project is editable. This makes document access more consistent and reduces confusion for external users collaborating on projects.
Original PR description
**Before this commit:** Currently, documents are available to portal users when the project is shared in read-only, but not when it is shared in editable. It is inconsistent and prevents portal users from easily accessing their documents. **In this commit:** - A new computed field shared_document_count added to project.task containing the number of shared_documents_ids. - A new stat button is added to project.task in portal view showing the number of shared documents and redirecting to shared documents page. task-3092925