Barcode scanning in Point of Sale no longer opens the product configuration popup when a product has only one available attribute option. This makes checkout faster and avoids unnecessary cashier interruptions.

Before this commit, scanning the barcode of a product with attributes set to never creation type, but with only one option available, would still trigger the product configuration popup.

opw-4754801

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Event badges with long event names now keep the QR code separate from the badge text. This prevents printed badges from becoming unreadable and helps event check-in materials remain usable.

Steps to reproduce:
1. Go to Events.
2. Create a new event with a long name.
3. Add a product.
4. Print the "Badge Example".

Issue:
When printing a badge from an event with a long name, the QR code overlaps or clips the information above it, making the badge unreadable.

Cause:
The issue is due to the large font size used for the event name.

Solution:
Reduced the font size of the event title to fs-5 to ensure enough spacing is maintained between the text and the QR code, avoiding layout overlap.

opw : 4783750

Before FIX:
![image](https://github.com/user-attachments/assets/bff09804-7824-454a-9523-1834ee0af4f4)

After FIX:
![image](https://github.com/user-attachments/assets/a85b1df9-c2e9-4f67-b99c-fb3f207702a3)

This fixes a problem in the website live chat test flow that was causing automated build checks to fail. It helps keep the release validation process stable without changing the user-facing live chat experience.

Runbot Build Error: https://runbot.odoo.com/odoo/runbot.build.error/111747





---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Changing the style of selected link text in the editor no longer causes an error. This makes formatting links more reliable for users working in apps such as To-do.

Steps to Reproduce:

1. Go to the To-do module.
2. Create a link.
3. Select the entire content using Ctrl + A.
4. Change the font style from 'Normal' to another (e.g., 'Header 1').
5. A traceback is thrown, although the link’s font style is changed.

Description of the issue/feature this PR addresses:

- The issue was caused by the presence of a `FEFF` (zero-width no-break space) character inside the selected text. This caused a conflict during selection restoration after the font style change. The clean handler was being triggered after the font change attempt, which led to an invalid cursor state.

 Current behavior before PR:
- A Traceback occurred when changing the font style of a selected link text.

Desired behavior after PR is merged:

- The clean handler is now explicitly called before the font change tries to restore the cursor, avoiding the invalid range or selection error.

task-4743390

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This fix prevents a Kenya payroll accounting test from failing when the separate SHIF payroll component is not installed. It improves reliability for single-app deployments without changing payroll behavior for end users.

## Version:
17.0+

## Issue:
Test (introduced by task 4457038) fails on Single App because of missing dependency.
Relies on SHIF_AMOUNT
https://github.com/odoo/enterprise/blob/ffb0aa8d7aad913328bb0b585197172da4e838b3/l10n_ke_hr_payroll_shif/data/hr_salary_rule_data.xml#L46C1-L47C1

runbot-159825

For proper provision management we introduce accounts 2350 and 2351 task-4797323 Forward-Port-Of: odoo/odoo#210062

For proper provision management we introduce accounts 2350 and 2351

task-4797323

Forward-Port-Of: odoo/odoo#210062

### Issue In project sharing, tasks in the "Done" and "Approved" stages were not shown with distinct progress in the Kanban progress bar. As a result, users were unable to identify the task status easily. ### Reason: The color class was set incorrectly. ### Fix: We have updated the color class in this commit to correctly reflect the task stages. issue-https://github.com/odoo/odoo/commit/1a44b849970d3e39111a99ea35db5b586b184dd3 ### Steps to Reproduce: - Create a projec

### Issue
   In project sharing, tasks in the "Done" and "Approved" stages were not shown with distinct progress in the Kanban progress bar. As a result, users were unable to identify the task status easily.

### Reason:
   The color class was set incorrectly.

### Fix:
   We have updated the color class in this commit to correctly reflect the  task stages.
  issue-https://github.com/odoo/odoo/commit/1a44b849970d3e39111a99ea35db5b586b184dd3

### Steps to Reproduce:
  - Create a project with 2 tasks:
      - Task 1 in the "Done" stage
      - Task 2 in the "Approved" stage
  - Share the project with a portal user
  - Open the project in the portal
  - Navigate to the project sharing Kanban view and check the progress bar

task-4551177

Forward-Port-Of: odoo/odoo#206031

Some services or applications (Outlook, Google Messages) display previews of links sent through messages or email. In an effort to strengten user privacy, these services fetch the previews from their own servers rather than from the user's device. Since these services' requests had not been added to the list of known bot identifiers, they generate parasite "clicks" which don't match their user. This commit adds identifiers for the Outlook and Google Messages service requests to the l

Some services or applications (Outlook, Google Messages) display
previews of links sent through messages or email. In an effort to
strengten user privacy, these services fetch the previews from their
own servers rather than from the user's device.

Since these services' requests had not been added to the list of
known bot identifiers, they generate parasite "clicks" which don't
match their user.

This commit adds identifiers for the Outlook and Google Messages
service requests to the list of known bot IDs, thereby preventing the
parasite clicks from generating.

task-3672491

Forward-Port-Of: odoo/odoo#200148
Forward-Port-Of: odoo/odoo#167799

Steps to reproduce: - When the planning module is not installed and we click on employee avatar - This leads to a traceback, especially when the related employee data is available only in hr.employee.public or hr.employee. Cause: - The avatar card component was using a hardcoded model instead of dynamically using props.record.model. Although a custom get_avatar_card_data method was introduced to centralize data logic, it was not implemented on all relevant models (hr.employee,

Steps to reproduce:
- When the planning module is not installed and we click on employee avatar
- This leads to a traceback, especially when the related employee data is
  available only in hr.employee.public or hr.employee.

Cause:
- The avatar card component was using a hardcoded model instead of dynamically
  using props.record.model.

 Although a custom get_avatar_card_data method was introduced to centralize data
 logic, it was not implemented on all relevant models (hr.employee,
 hr.employee.public), which caused traceback in  certain setups.

Solution:
- Replaced the hardcoded model with props.record.model to dynamically
  resolve the model.
- Added the get_avatar_card_data method to hr.employee.base to ensure
  compatibility.

Ensured the logic works correctly even when the planning module is not installed.

Follow-up to:
- Commit : https://github.com/odoo/odoo/pull/187171 https://github.com/odoo/enterprise/pull/75121
- prevent component destruction which moved avatar card data fetching into a parent method to avoid lifecycle issues.

Related task-4210513
task - 4777570

Forward-Port-Of: odoo/odoo#210027

To reproduce: ============= - have an employee with a working schedule of night shifts like 18:00 to 00:00 break to 01:00 then continue to 03:00 - create payslip for this employee for January 2025 - print the payslip, the working hours will be 183.9936 The problem: ============ 00:00 is represented as 23:59:59.99999 in python, that missing microsecond impacts the computation of the duration of the work entry. The solution: ============= round the total seconds opw-4702410 ---

To reproduce:
=============
- have an employee with a working schedule of night shifts like 18:00 to 00:00 break to 01:00 then continue to 03:00
- create payslip for this employee for January 2025
- print the payslip, the working hours will be 183.9936

The problem:
============
00:00 is represented as 23:59:59.99999 in python, that missing
microsecond impacts the computation of the duration of the work entry.

The solution:
=============
round the total seconds

opw-4702410
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#208811

Fixes an issue when issuing self-billed invoices to the platform. So far we have been using Odoo's bill name as ID, but we should instead use the bill reference (if set) to use the supplier number. task-4777585 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#208721

Fixes an issue when issuing self-billed invoices
to the platform.
So far we have been using Odoo's bill name as ID,
but we should instead use the bill reference (if
set) to use the supplier number.

task-4777585

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#208721

The aim of this commit is to: - avoid reporting negative amount in a 281.50 form which are rejected by the administration. - avoid reporting form with 0 value everywhere which are rejected by the administration. - avoid reporting a form with an amount < 250 EUR Context: The administration stated that we don't need to make any report that would be above 250 EUR. (art. 57, al. 3 CIR 92 et art. 30 AR/CIR 92) https://www.wolterskluwer.com/fr-be/expert-insights/tax-form-281-50

The aim of this commit is to:
    - avoid reporting negative amount in a 281.50 form which are rejected by the administration.
    - avoid reporting form with 0 value everywhere which are rejected by the administration.
    - avoid reporting a form with an amount < 250 EUR

Context:
The administration stated that we don't need to make any report that would be above 250 EUR.
(art. 57, al. 3 CIR 92 et art. 30 AR/CIR 92)

https://www.wolterskluwer.com/fr-be/expert-insights/tax-form-281-50 https://travaillerensociete.indicator.be/main/newsadvice/52784/news/52785/news_story/533/ https://www.monastucesetconseils.be/2025-04/fiches-fiscales-281-50-pour-le-29-juin-2025-WAACPCAR_EU33150802

Before this commit:
Odoo could create a form with a negative amount as commission/fee/... This could result in the administration software converting the xml into a BOW file to generated an error and a file that will be rejected by Belcotax.
Same for form with 0 everywhere.

Also, accountants always end up deleting the 281.50 form below 250 EUR as those don't need to be reported.

After this commit:
Odoo don't report negative or null total amount as commission/fee/... and doesn't create any form if the total amounts are below 250 EUR saving accountants the burden to remove them.

task-id: None
This was discussed and done with TSB and DELC and is also the result of our past experiences reporting 281.50 forms which also involved CAHE, MAKR and CAL.

Forward-Port-Of: odoo/enterprise#85508

Before this commit: Some of the names in the stock_type list were wrong, causing an invalid type error when validating delivery. After the commit: Added a lookup table to update the incorrect names to match names in FedEx documentation. Fedex docs: https://developer.fedex.com/api/en-is/catalog/ship/docs.html opw-4725488 Forward-Port-Of: odoo/enterprise#84762

Before this commit:

Some of the names in the stock_type list were wrong, causing an invalid type error when validating delivery.

After the commit:

Added a lookup table to update the incorrect names to match names in FedEx documentation.

Fedex docs: https://developer.fedex.com/api/en-is/catalog/ship/docs.html

opw-4725488

Forward-Port-Of: odoo/enterprise#84762

Implement new Swiss municipality OFS number assignment for ERP systems based on 2025 AFC list. This commit updates the address validation and municipality assignment logic in the ERP system to align with the new "Liste des communes OFS 2025 pour l’attribution du numéro de commune au code postal" published by the Swiss Federal Tax Administration (AFC) for withholding tax purposes. Forward-Port-Of: odoo/enterprise#84859

Implement new Swiss municipality OFS number assignment for ERP systems based on 2025 AFC list. This commit updates the address validation and municipality assignment logic in the ERP system to align with the new "Liste des communes OFS 2025 pour l’attribution du numéro de commune au code postal" published by the Swiss Federal Tax Administration (AFC) for withholding tax purposes.

Forward-Port-Of: odoo/enterprise#84859

For proper provision management we introduce accounts 2350 and 2351 task-4797323 Forward-Port-Of: odoo/enterprise#85574

For proper provision management we introduce accounts 2350 and 2351

task-4797323

Forward-Port-Of: odoo/enterprise#85574

Fix a bug where account moves paid with cash appears in a line with full 0 in the boe export of mod347 tax report. But it shouldn't create a line at all, so this commit remove the lines in this case. task-4613012 Forward-Port-Of: odoo/enterprise#84317

Fix a bug where account moves paid with cash appears in a line with full 0 in the boe export of mod347 tax report. But it shouldn't create a line at all, so this commit remove the lines in this case.

task-4613012

Forward-Port-Of: odoo/enterprise#84317

When timezone of user is empty and the user clicks on Add Closing Day(s) button, a traceback will appear. Steps to reproduce the error: - Open Profile > Preferences > Select empty in timezone > Save - Install ``Appointments`` - Go to Appointments > Schedule > Resource Bookings > Add Closing Day(s) Traceback: ``` File "/home/odoo/src/enterprise/appointment/wizard/appointment_manage_leaves.py", line 19, in <lambda> leave_start_dt = fields.Datetime('Start Date', required=True, defa

When timezone of user is empty and the user clicks on Add Closing Day(s) button,
a traceback will appear.

Steps to reproduce the error:
- Open Profile > Preferences > Select empty in timezone > Save
- Install ``Appointments``
- Go to Appointments > Schedule > Resource Bookings > Add Closing Day(s)

Traceback:
```
File "/home/odoo/src/enterprise/appointment/wizard/appointment_manage_leaves.py", line 19, in <lambda>
    leave_start_dt = fields.Datetime('Start Date', required=True, default=lambda self: self._default_time(0, 0))
  File "/home/odoo/src/enterprise/appointment/wizard/appointment_manage_leaves.py", line 14, in _default_time
    user_timezone = pytz.timezone(self.env.user.tz or self.env.context.get('tz', 'utc'))
  File "/home/odoo/src/odoo/odoo/_monkeypatches/pytz.py", line 129, in timezone
    return original_pytz_timezone(name)
  File "__init__.py", line 183, in timezone
    if zone.upper() == 'UTC':
AttributeError: 'bool' object has no attribute 'upper'
```

https://github.com/odoo/enterprise/blob/2c938b66fc1b526a360f4b199a47bcc53991bcb9/appointment/wizard/appointment_manage_leaves.py#L14
When the user selects an empty timezone, tz will be False.
So, It will lead to the above traceback.

Forward port https://github.com/odoo/enterprise/pull/64948 was closed in master,
so the issue is still present in saas-17.4 and all later versions.

sentry-6537084290

Forward-Port-Of: odoo/enterprise#83363

This commit will do a backport of the python change made in this commit: https://github.com/odoo/enterprise/pull/77565/commits/7f26eefa932ec09297fbc4b8256ebe0b2976b231 task-4476707 Forward-Port-Of: odoo/enterprise#84728

This commit will do a backport of the python change made in this commit: https://github.com/odoo/enterprise/pull/77565/commits/7f26eefa932ec09297fbc4b8256ebe0b2976b231

task-4476707

Forward-Port-Of: odoo/enterprise#84728