Wednesday, October 22, 2025
7 changes · 17.0
Enhancements to existing features
This update suppresses misleading warning messages caused by a packaging issue on Ubuntu Jammy environments. It keeps logs cleaner and helps teams focus on real operational issues without changing business functionality.
Original PR description
Apparently on jammy the pdfminer package returns nonsensical versions (the distribution for `pdfminer.six` yields `-VERSION-`, and inside the python code the `__version__` is `__VERSION__`). When trying to look up the distribution for the (invalid as a distribution name) `ldap`, as a fallback `pkg_resources` parses every package on the sys.path before returning a lookup failure. Doing so, it encounters `pdfminer` fails to parse its version as a `Version`, warns that that is deprecated, then parses it using the more lenient `LegacyVersion` and warns that this is also deprecated. Since this is a packaging issue in just jammy and we can't really do anything about it, just sweep the issue under the rug. https://runbot.odoo.com/odoo/error/163677
Resolved issues and error corrections
This fix prevents module updates from failing when users have edited or duplicated default UTM tracking names such as LinkedIn. It protects business continuity by allowing updates to complete without triggering uniqueness conflicts in marketing tracking data.
Original PR description
Steps to reproduce: 1) Install utm module. 2) In link tracker edit utm named LinkedIn or any and add another with same name. 3) update the module. We get an error that utm_medium or utm_source should be unique. create goes through `_get_unique_names` method so its only a problem when updating the record. 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#202567
Miscellaneous changes
This pull request corrects a minor typo in the Spanish translation. The term "Concepto Nota de Crédito" was missing the accent on "Crédito". This fix improves visual consistency and translation accuracy in the l10n_co_edi module.
Original PR description
This pull request corrects a minor typo in the Spanish translation. The term "Concepto Nota de Crédito" was missing the accent on "Crédito". This fix improves visual consistency and translation accuracy in the l10n_co_edi module.
The work center efficiency button now uses the same underlying figures as the detailed report, so managers see consistent OEE values in both places. This avoids confusion when reviewing manufacturing performance and also slightly streamlines the calculation.
Original PR description
**Current behavior:** The form view for a workcenter has an OEE smart button which can display a different value from the real OEE displayed by the `mrp_workcenter_productivity_report_oee` displayed…
**Current behavior:** The form view for a workcenter has an OEE smart button which can display a different value from the real OEE displayed by the `mrp_workcenter_productivity_report_oee` displayed when actually clicking the button and looking at the report. **Expected behavior:** Same values **Steps to reproduce:** 1. Make a workcenter and a BoM with an operation performed at the workcenter 2. Use the BoM in an MO such that there is some un-productive time (e.g., recorded production duration takes longer than expected duration) * example: 0:20 expected, 1:01 actual 3. Go to the workcenter list view -> click on the created workcenter -> look at OEE smart button display value -> click on it to see report -> report values are different **Cause of the issue:** the `oee` field on the workcenter is computed with rounded intermediary `blocked_time` and `productive_time` values, the actual report uses the raw values. **Fix:** Don't use the rounded intermediary values in computing `oee`. Post-this-diff, we actually do one less `_read_group` (along with computing a more accurate field value). opw-4795463
The Helpdesk SLA reporting view now keeps the SLA status available as a grouping option after users remove the default grouping. This avoids forcing users to reload the report to get back to the original view organization.
Original PR description
Currently, when the user opens the sla reporting view, if he removes the default grouping of sla_status, he has no way to get it back unless he reloads the view completly. This commit fixes this issue by adding the sla_status field to the group_by options. task-5076401
The Field Service “To Schedule” view now excludes tasks that are already done or cancelled. This keeps scheduling lists focused on active work that still needs assignment or planning, reducing confusion for teams.
Original PR description
**steps to reproduce:** Go to field service Go to all tasks > to schedule **issue:** The To Schedule filter was also displaying tasks in cancelled or done state, whereas it should only show open tasks that need to be scheduled or assigned. **cause:** The filter domain did not exclude cancelled/done state, causing closed tasks to appear in the filtered view. **fix:** Updated the filter domain to exclude cancelled/done state, to ensure only open tasks are shown under the To Schedule filter. task-5138590
This pull request corrects a minor typo in the Spanish translation. The term "Concepto Nota de Crédito" was missing the accent on "Crédito". This fix improves visual consistency and translation accuracy in the l10n_co_edi module.
Original PR description
This pull request corrects a minor typo in the Spanish translation. The term "Concepto Nota de Crédito" was missing the accent on "Crédito". This fix improves visual consistency and translation accuracy in the l10n_co_edi module.