Todo:
- [x] complete the 2 custom filters (finish up the WIP js)
- [x] PDF export (aims the GL for some reason, should be simple targeting the selected_section_id or smth)
- [x] CSV export (simple)
~~- [ ] make `_build_custom_columns()` into a parent helper (and give it a better name) with GJ~~
- [x] handle the changes in https://github.com/odoo/enterprise/pull/102950 if merged before
  - [x] ^ stuff like the updated `method_number`
- [ ] https://github.com/odoo/enterprise/pull/102808
---

## [ADD] l10n_ph_reports_asset: Subsidiary BOA - Fixed Asset Listing

This commit adds the Fixed Asset Listing (FAL) subsidiary report to the
Book of Accounts. It, like all other BoA reports, supports export in
.csv and .pdf formats as required by the BIR.

This report introduces 2 custom filters for Asset Status and Asset
Models that are fully-supported in the PDF export.

--- 
Technical Choices:
- **Entity-First Strategy:** Unlike standard transaction-based reports
  (GL), this report uses a registry-based query (`FROM account_asset`).
  This ensures visibility for historical assets with no current
  depreciation), indefinite-life assets (e.g., Land), and simulated
  assets.
- **Date Overlap Logic:** The date range filtering will show assset
  lines that are running or projected to run. We determine asset end of
  life by disposal date (if applicable) or useful life. We also handle
  infinite life assets (method_number = 0).
- **Custom Filters**: They are designed as dropdown selects with UI
  behavior mimicing filter_journal. Supports multi-company. Asset Model
  filter will be hidden if there are no Asset Models created.
- We deduplicate column values across colgroups for ease of reading.
- Accumulated Depreciation column will only show depreciation AMLs. This
  excludes modifications to depreciations such as selling and disposal.

Changes summary:
- Add `l10n_ph.boa.fal.report.handler` abstract model.
- Add `L10nPhBoaFalReportFilters` and it's PDF export display
- Add CSV and PDF export templates.

Testing/Verification:
Includes snapshot testing of the web view and csv export data and some
extra tests to check for these features:
- Indefinite life assets (e.g., Land with 0 duration)
- Historical assets (acquired years ago, still running)
- Future/Simulated assets (Draft state with analytic distribution)
- Custom filters work as intended

task-[5419877](https://www.odoo.com/odoo/action-4043/5419877)

### Issue:
Having a calendar with a timezone different from utc and looking at the planning gantt view, the hours displayed in the "Total" row are wrong.

### Steps to reproduce:
- Have an employee with a calendar in "Europe/Brussels" and working from 8 to 17
- In planning add a line for this employee
- Display the gantt view on a day
- Create a shift for this employee from 8 to 17
- In the "Total" row, the first hour is not counted

### Cause:
To compute the values displayed in the Total row, we take the intersection of the shift and the working hours from the calendar. ([src](https://github.com/odoo/enterprise/blob/2b887d094c66be7aebd92fbf735b1852f5dde4b5/planning/static/src/views/planning_gantt/planning_gantt_renderer.js#L318)) But the working hours from the calendar are given in UTC for this computation (without conversion), this result in a discrepancy between the actual hours of the calendar (with timezone conversion) and the one given to compute the total row.

### Solution:
`resource_work_intervals()` returns the work intervals with the calendar hours and the resource timezone.

In our case, only the hours are interesting (the previous code replaced the timezone by UTC). We need to convert them from the calendar timezone to UTC. So the first thing to do is remove the timezone from `resource_work_interval` then we localize it in the calendar timezone and to finish we convert it to UTC.

opw-5564749

Forward-Port-Of: odoo/enterprise#108369
Forward-Port-Of: odoo/enterprise#106891

Currently, an error occurs when a user opens the Tax Returns report.

**Steps to Reproduce:**

 - Install the `Accounting` module.
 - Go to `Journal Entries` and create a journal entry with lines, `Ex:`
   - One `Receivable` line with a positive debit.
   - One `Income` line with the same credit.
 - `Post` the journal entry.
 - Go to `Accounting > Closing > Tax Returns`.
 - Set the `date` and click `Apply`.

`AssertionError: Invalid falsy real id`

When opening the Tax Returns report, it going generates the Annual Closing Checklist. During this 
process, it tries to get the unknown partner’s account line ID [1]. However, if the line_id does not 
contain anything related to the target model (account.move.line), the method returns None [2]. Later, 
it attempts to browse using this None value which raise the error [3].

This commit ensures that only valid ids are added, preventing None values from being browsed.

[1]: https://github.com/odoo/enterprise/blob/887fb85cf3ed488187418c03df159af859a4e435/account_reports/models/account_return.py#L2365-L2371

[2]: https://github.com/odoo/enterprise/blob/887fb85cf3ed488187418c03df159af859a4e435/account_reports/models/account_report.py#L2461

[3]: https://github.com/odoo/enterprise/blob/887fb85cf3ed488187418c03df159af859a4e435/account_reports/models/account_return.py#L2399

sentry-7263718845

Forward-Port-Of: odoo/enterprise#107524

Followup to previous fix: 705e27a2d3d9e3c4d075a1e8fb599333a504a316 

If the user configured his database with more than one Buy or Manufacture route, the `_get_route_domain` would trigger a Singleton Error.

# Steps to Reproduce:
- Create new Manufacture Route:
  - Create new Warehouse W2
  - Create new 'Manufacture 2' route (no rule yet)
  - Go to the 'Manufacture' route
  - Select the new rule for W2, expand popup
  - Update the route to 'Manufacture 2'
- Create new Product P
  - Storable
  - Create Basic BoM
- Product form -> Actions wheel -> Replenish => Singleton Error

OPW-5960493

---

## Configuration
<img width="1844" height="628" alt="image" src="https://github.com/user-attachments/assets/b90c070c-4af5-427c-bd3d-79904a7881a0" />


## Traceback
```
RPC_ERROR

Odoo Server Error

Occured on 102180409-19-0-design-theme.runbot119.odoo.com on model product.replenish on 2026-02-25 08:12:03 GMT

Traceback (most recent call last):
  File "/data/build/odoo/odoo/http.py", line 2273, in _serve_db
    return service_model.retrying(serve_func, env=self.env)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/service/model.py", line 185, in retrying
    result = func()
             ^^^^^^
  File "/data/build/odoo/odoo/http.py", line 2328, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/http.py", line 2543, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/addons/base/models/ir_http.py", line 355, in _dispatch
    result = endpoint(**request.params)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/http.py", line 788, in route_wrapper
    result = endpoint(self, *args, **params_ok)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/web/controllers/dataset.py", line 32, in call_kw
    return call_kw(request.env[model], method, args, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/service/model.py", line 94, in call_kw
    result = method(recs, *args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/web/models/models.py", line 1964, in onchange
    defaults = self.default_get(missing_names)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/purchase_stock/wizard/product_replenish.py", line 12, in default_get
    res = super().default_get(fields)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/stock/wizard/product_replenish.py", line 77, in default_get
    res['route_id'] = self.env['stock.route'].search(self._get_route_domain(product_tmpl_id), limit=1).id
                                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/purchase_stock/wizard/product_replenish.py", line 92, in _get_route_domain
    domain = super()._get_route_domain(product_tmpl_id)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/mrp/wizard/product_replenish.py", line 51, in _get_route_domain
    domain = Domain.OR([domain, Domain('id', '=', manufacture_route.id)])
                                                  ^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/orm/fields_misc.py", line 114, in __get__
    raise ValueError("Expected singleton: %s" % record)
ValueError: Expected singleton: stock.route(6, 20)
```


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

Forward-Port-Of: odoo/odoo#250580

1. Create a contact (with minimal details).
2. Create a customer invoice for that contact **last month** with `quantity = 300`.
3. Create a credit note for that invoice **this month**.
4. Create another customer invoice for the same contact **this month** with `quantity = 100`.

In the FAIA report (XML), within the General Ledger section, the partner is incorrectly classified as a supplier instead of a customer.

In the method _saft_fill_report_partner_ledger_values from account_saft, he partner type is determined based on whether the balance is negative.

However, a negative balance can result from a credit note, where the partner is still a customer and not a supplier. Furthermore, a partner can be both a supplier and a customer.

This commit allows a partner to be both a customer and a supplier. If both receivable and payable are 0 we set the partner type to customer to keep the behavior from e9640caf29e967fe7d8c6fe303b5a8d7a866437e

opw-5360924

Forward-Port-Of: odoo/enterprise#108197
Forward-Port-Of: odoo/enterprise#100749

Step to reproduce:
- have a trusted pos and a loyalty program which gives points per $ spent
- start pos and select order and a partner (he should already have some LPs)
- notice the loyalty points assgined
- save the order, you are redirected to new order
- switch back to original order

Observation:
- Notice, the loyalty points are reassigned for example :
- if initially partner's LP = 50,  product added is 100$ , LP = 50+100 = 150
- After saving, LP becomes 150 + 100 = 250

Cause:
- LP's are processed after every `sync_from_ui` call from `_postProcessLoyalty` which updates the customer's lp, even before the order is fullfilled or when order is still in `draft` state

Fix:
- Issue is fixed in https://github.com/odoo/odoo/commit/a4b37ec474656c7af23d0134251d589e9a6a61ca
- This commit adds related test for the fix
    

opw-5609964

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

Forward-Port-Of: odoo/odoo#248420
Forward-Port-Of: odoo/odoo#245400

Steps to reproduce:
- Set up a Company with BR localization
- Create a product as follows:
  - [General Information] Product Type: Service
  - [Sales] LC116 Code: 14.01
  - [Sales] Purpose of Use: Not applicable
  - [Sales] Service Code Origin: 14.01.3/168061/1524
  - [Sales] Service Codes: 14.01.3/168061/1524
- Create an Invoice with Document Type "Electronic Service Invoice - NFS-e"
- Add the product on the line
- Compute taxes
- Compute taxes again

Issue:

Action will be blocked by a validation error resulting from the external
taxes call
```
odoo.exceptions.ValidationError: Odoo could not fetch the taxes related to Draft Invoice.
Errors: Rejection: Total Installments doesnt match Total Lines
∑ installments[m]grossValue - ∑ (lines[n].lineAmount-line[n].lineTaxedDiscount) <> 0
```

It occurs because during the call the system is considering the
existing taxes on the line and it will send to the avatax service wrong
amounts

opw-5412456
opw-5409735

Forward-Port-Of: odoo/enterprise#108403
Forward-Port-Of: odoo/enterprise#108088

When syntax error will raise ``node`` will not assign. So, assign ``None`` before error will surpess.

Note:- found it during testing. 

```
Traceback (most recent call last):
  File "/home/odoo/src/odoo/19.0/odoo/http.py", line 2273, in _serve_db
    return service_model.retrying(serve_func, env=self.env)
  File "/home/odoo/src/odoo/19.0/odoo/service/model.py", line 185, in retrying
    result = func()
  File "/home/odoo/src/odoo/19.0/odoo/http.py", line 2328, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "/home/odoo/src/odoo/19.0/odoo/http.py", line 2543, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "/home/odoo/src/odoo/19.0/odoo/addons/base/models/ir_http.py", line 355, in _dispatch
    result = endpoint(**request.params)
  File "/home/odoo/src/odoo/19.0/odoo/http.py", line 788, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "/home/odoo/src/odoo/19.0/addons/web/controllers/dataset.py", line 32, in call_kw
    return call_kw(request.env[model], method, args, kwargs)
  File "/home/odoo/src/odoo/19.0/odoo/service/model.py", line 94, in call_kw
    result = method(recs, *args, **kwargs)
  File "/home/odoo/src/odoo/19.0/addons/web/models/models.py", line 113, in web_read
    values_list: list[dict] = self.read(fields_to_read, load=None)
  File "/home/odoo/src/odoo/19.0/odoo/orm/models.py", line 3490, in read
    return self._read_format(fnames=fields, load=load)
  File "/home/odoo/src/odoo/19.0/odoo/orm/models.py", line 3747, in _read_format
    vals[name] = convert(record[name], record, use_display_name)
  File "/home/odoo/src/odoo/19.0/odoo/orm/models.py", line 6686, in __getitem__
    return self._fields[key].__get__(self)
  File "/home/odoo/src/odoo/19.0/odoo/orm/fields.py", line 1746, in __get__
    self.compute_value(recs)
  File "/home/odoo/src/odoo/19.0/odoo/orm/fields.py", line 1917, in compute_value
    records._compute_field_value(self)
  File "/home/odoo/src/odoo/19.0/odoo/orm/models.py", line 4952, in _compute_field_value
    determine(field.compute, self)
  File "/home/odoo/src/odoo/19.0/odoo/orm/fields.py", line 81, in determine
    return needle(*args)
  File "/home/odoo/src/odoo/19.0/odoo/addons/base/models/ir_ui_view.py", line 366, in _compute_invalid_locators
    if invalid_locator := assess_locator(source, spec):
  File "/home/odoo/src/odoo/19.0/odoo/addons/base/models/ir_ui_view.py", line 330, in assess_locator
    if node is None:
UnboundLocalError: local variable 'node' referenced before assignment
```
opw-5956964





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

Forward-Port-Of: odoo/odoo#250589

**Steps to reproduce:**
- Install 'account_iso20022', 'l10n_ch' and switch to a Swiss company
- Have a bank with a BIC number and an account for that bank with a clearing number
- Create a vendor bill for a Swiss partner or payrun report
- Pay with "Swiss ISO20022" > generate xml pain001
- Validate against xsd or any swiss pain001 test plateform > Incorrect rules usage ! not valid xml !

**Cause:**
In the XML the field BIC and ClrSysMmbId are present. Only one of them can be present. See the [documentation (page 27 and 33)](https://www.six-group.com/dam/download/banking-services/interbank-clearing/fr/standardization/iso/swiss-recommendations/archives/implementation-guidelines-ct/implementation-guidelines-ct_v1_6_1.pdf).

**Solution:**
Create the method `_get_ClrSysMmbId()` which will only return for Swiss if there is no BIC number. This is a partial unrevert of [this commit](https://github.com/odoo/enterprise/commit/177c7bbc890c3d142010de2cb7d0d9d6752c7fd9#diff-282e44e861d61542f3bc6d40e61b73fd1556f659d53ecd8bf9430dcec79c2fd6).

opw-4872507

Forward-Port-Of: odoo/enterprise#108461

Currently, an error occurs when user tries to validate a domain with no field name.

Steps to install:
- Install `sale_management` > Open sale order list view > Turn on debug mode.
- Click on search bar > Custom filter > Click on field and remove its field name written below the list of fields.
- Click validate.

Error:
```
TypeError: Empty field name in condition ('', '=', 1)
```

Cause:
- As the field name was emptied by the user the [line] will raise a TypeError during the domain validation.
- Till `19.0` any error during domain validation was handled  through [here] which was later changed to handle only ValueErrors through this [commit].

Solution:
- Handled TypeErrors during domain validation.

[line]: https://github.com/odoo/odoo/blob/260b9c0417ed2278429fcdd7f50d61786d4e9beb/odoo/orm/domains.py#L841

[here]: https://github.com/odoo/odoo/blob/a220fb71c036c93fa1e75d4d37127e5eda0118f9/addons/web/controllers/domain.py#L34

[commit]: https://github.com/odoo/odoo/commit/a1434c32e9f4dd226d512677fd96e3051b908d8b#diff-e5da86414a8020b2843fb359453238e4977027d30f73f1fa792ca63ddd8fa2a7L34-R23

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

Forward-Port-Of: odoo/odoo#249993

**Steps to reproduce:**
- Install 'account_iso20022', 'l10n_ch' and switch to a Swiss company
- Have a bank with a BIC number and an account for that bank with a clearing number
- Create a vendor bill for a Swiss partner or payrun report
- Pay with "Swiss ISO20022" > generate xml pain001
- Validate against xsd or any swiss pain001 test plateform > Incorrect rules usage ! not valid xml !

**Cause:**
In the XML the field BIC and ClrSysMmbId are present. Only one of them can be present. See the [documentation (page 27 and 33)](https://www.six-group.com/dam/download/banking-services/interbank-clearing/fr/standardization/iso/swiss-recommendations/archives/implementation-guidelines-ct/implementation-guidelines-ct_v1_6_1.pdf).

**Solution:**
Create the method `_get_ClrSysMmbId()` which will only return for Swiss if there is no BIC number. This is a partial unrevert of [this commit](https://github.com/odoo/enterprise/commit/177c7bbc890c3d142010de2cb7d0d9d6752c7fd9#diff-282e44e861d61542f3bc6d40e61b73fd1556f659d53ecd8bf9430dcec79c2fd6).

opw-4872507

Forward-Port-Of: odoo/enterprise#108461

On delivery slip, the total weight of a package doesn't include the weight of the product in the outermost package.

Steps to reproduce:
-------------------
* Create a Package "Pa" with a package type that has a weight
* Create a product "Po" tracked by quantity
* Add two units of the product Po to the package Pa
* Create Delivery with two units of Po.
* Confirm the Delivery and print the delivery slip -> The total weight is the weight of the package type without including the products inside.

Observation:
-------------
When computing the shipping_weight for the delivery, it will fallback on the package_weight to calculate it weight, https://github.com/odoo/odoo/blob/ca14f1aa21a75398919c1453be19011522bb3b5c/addons/stock/models/stock_picking.py#L893-L906 
It retrieve the weight calculated by _get_weight
https://github.com/odoo/odoo/blob/93fa6d9fff63534cfa9251e21fc82797d8b83468/addons/stock/models/stock_package.py#L435
Except for the outermost package,  where it incorrectly considers only the package type weight and does not include the products weight

opw-5499770

Forward-Port-Of: odoo/odoo#247227

Followup to previous fix: 705e27a2d3d9e3c4d075a1e8fb599333a504a316 

If the user configured his database with more than one Buy or Manufacture route, the `_get_route_domain` would trigger a Singleton Error.

# Steps to Reproduce:
- Create new Manufacture Route:
  - Create new Warehouse W2
  - Create new 'Manufacture 2' route (no rule yet)
  - Go to the 'Manufacture' route
  - Select the new rule for W2, expand popup
  - Update the route to 'Manufacture 2'
- Create new Product P
  - Storable
  - Create Basic BoM
- Product form -> Actions wheel -> Replenish => Singleton Error

OPW-5960493

---

## Configuration
<img width="1844" height="628" alt="image" src="https://github.com/user-attachments/assets/b90c070c-4af5-427c-bd3d-79904a7881a0" />


## Traceback
```
RPC_ERROR

Odoo Server Error

Occured on 102180409-19-0-design-theme.runbot119.odoo.com on model product.replenish on 2026-02-25 08:12:03 GMT

Traceback (most recent call last):
  File "/data/build/odoo/odoo/http.py", line 2273, in _serve_db
    return service_model.retrying(serve_func, env=self.env)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/service/model.py", line 185, in retrying
    result = func()
             ^^^^^^
  File "/data/build/odoo/odoo/http.py", line 2328, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/http.py", line 2543, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/addons/base/models/ir_http.py", line 355, in _dispatch
    result = endpoint(**request.params)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/http.py", line 788, in route_wrapper
    result = endpoint(self, *args, **params_ok)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/web/controllers/dataset.py", line 32, in call_kw
    return call_kw(request.env[model], method, args, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/service/model.py", line 94, in call_kw
    result = method(recs, *args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/web/models/models.py", line 1964, in onchange
    defaults = self.default_get(missing_names)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/purchase_stock/wizard/product_replenish.py", line 12, in default_get
    res = super().default_get(fields)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/stock/wizard/product_replenish.py", line 77, in default_get
    res['route_id'] = self.env['stock.route'].search(self._get_route_domain(product_tmpl_id), limit=1).id
                                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/purchase_stock/wizard/product_replenish.py", line 92, in _get_route_domain
    domain = super()._get_route_domain(product_tmpl_id)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/mrp/wizard/product_replenish.py", line 51, in _get_route_domain
    domain = Domain.OR([domain, Domain('id', '=', manufacture_route.id)])
                                                  ^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/orm/fields_misc.py", line 114, in __get__
    raise ValueError("Expected singleton: %s" % record)
ValueError: Expected singleton: stock.route(6, 20)
```


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

Forward-Port-Of: odoo/odoo#250580

*:ae,au,bd,be,ch,eg,id,jo,ke,lt,lu,ma,my,nl,pk,pl,ro,sk,tr,us

When the ``Standard 40 hours/week`` working schedule is deleted
and the ``Payroll: Update data`` cron runs, a traceback is raised.

For ``l10n_us_hr_payroll`` module
Steps to reproduce the error:
- Install ``l10n_us_hr_payroll`` module with demo data
- Go to Employees > Configuration > Settings > Change Company Working Hours
- Go to Working Schedules > Delete ``Standard 40 hours/week`` working schedule
- Run the ``Payroll: Update data`` cron

Traceback:
```py
ValueError: External ID not found in the system: resource.resource_calendar_std

ParseError: while parsing /home/odoo/src/enterprise/l10n_us_hr_payroll/data/hr_payroll_structure_type_data.xml:3, somewhere inside <record id="structure_type_employee_us" model="hr.payroll.structure.type">
    <field name="name">United States: Employee</field>
    <field name="default_resource_calendar_id" ref="resource.resource_calendar_std"/>
    <field name="country_id" ref="base.us"/>
</record>
```

The ``Payroll: Update data`` cron updates payroll data that references
the ``Standard 40 hours/week`` working schedule.
If the user has deleted this working schedule, the external ID no longer exists,
leading to the above traceback.

sentry-7166574553

Forward-Port-Of: odoo/enterprise#106950

Steps to reproduce:
- Set up a Company with BR localization
- Create a product as follows:
  - [General Information] Product Type: Service
  - [Sales] LC116 Code: 14.01
  - [Sales] Purpose of Use: Not applicable
  - [Sales] Service Code Origin: 14.01.3/168061/1524
  - [Sales] Service Codes: 14.01.3/168061/1524
- Create an Invoice with Document Type "Electronic Service Invoice - NFS-e"
- Add the product on the line
- Compute taxes
- Compute taxes again

Issue:

Action will be blocked by a validation error resulting from the external
taxes call
```
odoo.exceptions.ValidationError: Odoo could not fetch the taxes related to Draft Invoice.
Errors: Rejection: Total Installments doesnt match Total Lines
∑ installments[m]grossValue - ∑ (lines[n].lineAmount-line[n].lineTaxedDiscount) <> 0
```

It occurs because during the call the system is considering the
existing taxes on the line and it will send to the avatax service wrong
amounts

opw-5412456
opw-5409735

Forward-Port-Of: odoo/enterprise#108403
Forward-Port-Of: odoo/enterprise#108088

When syntax error will raise ``node`` will not assign. So, assign ``None`` before error will surpess.

Note:- found it during testing. 

```
Traceback (most recent call last):
  File "/home/odoo/src/odoo/19.0/odoo/http.py", line 2273, in _serve_db
    return service_model.retrying(serve_func, env=self.env)
  File "/home/odoo/src/odoo/19.0/odoo/service/model.py", line 185, in retrying
    result = func()
  File "/home/odoo/src/odoo/19.0/odoo/http.py", line 2328, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "/home/odoo/src/odoo/19.0/odoo/http.py", line 2543, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "/home/odoo/src/odoo/19.0/odoo/addons/base/models/ir_http.py", line 355, in _dispatch
    result = endpoint(**request.params)
  File "/home/odoo/src/odoo/19.0/odoo/http.py", line 788, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "/home/odoo/src/odoo/19.0/addons/web/controllers/dataset.py", line 32, in call_kw
    return call_kw(request.env[model], method, args, kwargs)
  File "/home/odoo/src/odoo/19.0/odoo/service/model.py", line 94, in call_kw
    result = method(recs, *args, **kwargs)
  File "/home/odoo/src/odoo/19.0/addons/web/models/models.py", line 113, in web_read
    values_list: list[dict] = self.read(fields_to_read, load=None)
  File "/home/odoo/src/odoo/19.0/odoo/orm/models.py", line 3490, in read
    return self._read_format(fnames=fields, load=load)
  File "/home/odoo/src/odoo/19.0/odoo/orm/models.py", line 3747, in _read_format
    vals[name] = convert(record[name], record, use_display_name)
  File "/home/odoo/src/odoo/19.0/odoo/orm/models.py", line 6686, in __getitem__
    return self._fields[key].__get__(self)
  File "/home/odoo/src/odoo/19.0/odoo/orm/fields.py", line 1746, in __get__
    self.compute_value(recs)
  File "/home/odoo/src/odoo/19.0/odoo/orm/fields.py", line 1917, in compute_value
    records._compute_field_value(self)
  File "/home/odoo/src/odoo/19.0/odoo/orm/models.py", line 4952, in _compute_field_value
    determine(field.compute, self)
  File "/home/odoo/src/odoo/19.0/odoo/orm/fields.py", line 81, in determine
    return needle(*args)
  File "/home/odoo/src/odoo/19.0/odoo/addons/base/models/ir_ui_view.py", line 366, in _compute_invalid_locators
    if invalid_locator := assess_locator(source, spec):
  File "/home/odoo/src/odoo/19.0/odoo/addons/base/models/ir_ui_view.py", line 330, in assess_locator
    if node is None:
UnboundLocalError: local variable 'node' referenced before assignment
```
opw-5956964





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

Forward-Port-Of: odoo/odoo#250589

Firefox 148 fixed the behavior of `about:blank` documents, as explained
in their [release notes]:

> The initial about:blank document is now Web-compatible. If the first
> navigation of a browsing context goes to about:blank, it completes
> synchronously and is no longer replaced by a second parser-generated
> document.

Commit [e0796020] added the new page dialog in website, and used empty
iframes to load each page template.
Commit [edf81c13] added the add snippets dialog in website, and used an
empty iframe to load the snippets previews.
In both cases, before Firefox' fix, it meant we had to wait the
recreation of the 2nd document before proceeding. This is no longer the
case in Firefox >= 148.

[release notes]: https://www.firefox.com/en-US/firefox/148.0/releasenotes/
[e0796020]: https://github.com/odoo/odoo/commit/e0796020ee0c3188e1e9d9fa077de73a2211c6f7
[edf81c13]: https://github.com/odoo/odoo/commit/edf81c13d8f2f6d29a77d68cbfa0dc9216da3c2a

Forward-Port-Of: odoo/odoo#250592

### Steps to detect the bug:
  - Download stock apps
  - Enable "storage locations" settings under warehouse index
  - Change name of warehouse with a name composed only of numbers (ex. 01)
  - Create a product (with barcode number)
  - Insert a number of products available with smart button "on hand"
  - Create a new delivery for that product
  - Go to barcode app and search for the delivery you just created
  - Click on it and see that the name of the warehouse will be stock/01 instead of the correct 01/stock
    
### The problem:
The previous configuration used direction: rtl; on the warehouse name
element in the barcode app. So if the string contains only letters the
standard visual order is maintained, however, when the string consists
entirely of numbers the rtl property forces the browser to reorder them
from right to left.

### The reson to introduce the fix:
By removing this property, it is ensured that numerical warehouse codes are displayed in their natural sequence without being flipped.
    
opw-5730199

Forward-Port-Of: odoo/enterprise#107920

**Steps to reproduce:**
- Install l10n_ro_saft
- Switch to a Romanian company (e.g. RO Company)

- Create an asset model:
  * Method: Straight Line
  * Duration: 12 Months
- Configure a "Fixed Assets" account:
  * Automate Asset: Create and validate
  * Asset Model: [the asset model created above]
- Create a bill:
  * Vendor: [create a new vendor]
  * Bill Date: [last month]
  * Invoice Line: [A line with the fixed asset account]
- Confirm the bill

- Go to "Accounting / Reporting / Audit Reports / General Ledger"
- Select the current month (The fixed asset account should be present)
- In the cog menu, select "SAF-T (D406 Asset Declaration)"

**Issue:**
A traceback is raised while trying to display the name of a supplier.

**Cause:**
To display the supplier name of an asset, a dict having the id of the customer or supplier as key (i.e. partner_detail_map) is used. This dict is build by getting the list of all partners linked to a posted journal item on an asset (or liability) account in the period of the report.
In this case, it's the current month.
However, the created bill has been posted the month before.
So no journal item is found for the vendor that has been created just for the bill and therefore there is no key for him in the dict, which leads to the error when trying to get the id of the supplier of the asset in the dict.

**Solution:**
Instead of just fetching the posted entries linked to a receivable or payable account in order to get the list of the potential customers and suppliers, we also fetch the depreciation lines that are linked to an asset account and can still be in draft.


opw-5499918

Forward-Port-Of: odoo/enterprise#105987

Steps to Reproduce: https://www.awesomescreenshot.com/video/49329263?key=2daddfb65e4ee8dcf1a047c09c6bd2b5
- Install l10n_uk_reports module
- Keep the VAT value empty for the UK Company
- On the Tax Report (GB), click Connect to HMRC
- Establish connection with HMRC
- After a successful connection, try to send the tax report to HMRC
- Traceback will appear

<details><summary>Exact Traceback</summary>
<p>

```
RPC_ERROR

Odoo Server Error

Occured on 100710704-master-all.runbot216.odoo.com on model account.report on 2026-02-11 12:50:03 GMT

Traceback (most recent call last):
  File "/data/build/odoo/odoo/http/requestlib.py", line 632, in _serve_db
    return retrying(serve_func, env=self.env)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/http/retrying.py", line 52, in retrying
    result = func()
             ^^^^^^
  File "/data/build/odoo/odoo/http/requestlib.py", line 687, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/http/dispatcher.py", line 308, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/addons/base/models/ir_http.py", line 374, in _dispatch
    result = endpoint(**request.params)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/http/routing_map.py", line 207, in route_wrapper
    result = endpoint(self, *args, **params_ok)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/web/controllers/dataset.py", line 32, in call_kw
    return call_kw(request.env[model], method, args, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/service/model.py", line 57, in call_kw
    result = method(recs, *args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/enterprise/account_reports/models/account_report.py", line 2825, in dispatch_report_action
    return report_to_call.dispatch_report_action(options, action, action_param=action_param, on_sections_source=False)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/enterprise/account_reports/models/account_report.py", line 2836, in dispatch_report_action
    return report_method(model, *args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/enterprise/l10n_uk_reports/models/account_financial_report.py", line 30, in send_hmrc
    self.env['l10n_uk.vat.obligation'].import_vat_obligations(self.env.context['client_data'])
  File "/data/build/enterprise/l10n_uk_reports/models/hmrc_vat_obligation.py", line 124, in import_vat_obligations
    self._get_vat(),
    ^^^^^^^^^^^^^^^
  File "/data/build/enterprise/l10n_uk_reports/models/hmrc_vat_obligation.py", line 111, in _get_vat
    if vat.startswith(('GB', 'XI')):
       ^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'startswith'

The above server error caused the following client error:
RPC_ERROR: Odoo Server Error
    RPC_ERROR
        at makeErrorFromResponse (https://100710704-master-all.runbot216.odoo.com/web/assets/0a37914/web.assets_web.min.js:3225:165)
        at XMLHttpRequest.<anonymous> (https://100710704-master-all.runbot216.odoo.com/web/assets/0a37914/web.assets_web.min.js:3231:13)
```

</p>
</details> 

Reason:
- No VAT set on the current company.

Solution:
- Blocking level error for the user to set VAT on the current company.

Task-5929908

Forward-Port-Of: odoo/enterprise#107150

Clicking the Work Entries smart button raises a traceback when an overtime record has no Stop (time_stop).

Steps to reproduce the error:
- Install ``hr_work_entry_attendance`` module with demo data
- Activate developer mode
- Create an Employee A > Settings > Set Default Ruleset in Overtime Ruleset
  In Payroll Tab, Work Entry Source: ``Attendances`` and set Contract
- Create an overtime attendance > Save > Open the Overtime Details > Unset the ``Stop(time_stop)`` > Save
- Open Employee A > Click on Work Entries smart button

Traceback:
```py
TypeError: '<' not supported between instances of 'bool' and 'datetime.datetime'
```

https://github.com/odoo/enterprise/blob/56c3723a925f718ba39d11cde12933542ebcd7c1/hr_work_entry_attendance/models/hr_version.py#L49-L52
When ``stop(time_stop)`` is unset in the overtime,
``ot.time_stop`` is False,
causing ``min()`` to compare a ``datetime`` with ``False``, which raises the above traceback.

sentry-7169332615

Forward-Port-Of: odoo/enterprise#108392
Forward-Port-Of: odoo/enterprise#103764

**Steps to Reproduce:**
1 - create an employee in Belgium company with hourly rate 20.62 and 40h/week working schedule 2 - Set 10 paid time off to this employee
3 - Set 2000 euros in recovery amount holiday n-1
4 - Set 10 days in recovery day holiday n-1
5 - Employee takes 5 paid time off in February and 5 in December 6 - Do one payslip for this employee for February  and validate it 7 - Do one payslip for this employee for December

Current behaviour :
- the holiday n-1 amount for February = 824.80
- the holiday n-1 amount for December = 742.32

Expected behaviour :
- the holiday n-1 amount for December should be 20.62 (hourly_rate) * 5 (days) * 8 (hours) = 824.80

**Reason**
- The daily recovery amount was calculated using hardcoded standard working hours (38h/week) instead of the employee's actual schedule (40h/week), causing an incorrect deduction rate for non-standard schedules.

**Solution**
- Replace the hardcoded reference with the actual hours per week from the employee's resource calendar to ensure the correct hourly rate is applied.

Forward-Port-Of: odoo/enterprise#108104
Forward-Port-Of: odoo/enterprise#106205

Steps to Reproduce: https://www.awesomescreenshot.com/video/49329263?key=2daddfb65e4ee8dcf1a047c09c6bd2b5
- Install l10n_uk_reports module
- Keep the VAT value empty for the UK Company
- On the Tax Report (GB), click Connect to HMRC
- Establish connection with HMRC
- After a successful connection, try to send the tax report to HMRC
- Traceback will appear

<details><summary>Exact Traceback</summary>
<p>

```
RPC_ERROR

Odoo Server Error

Occured on 100710704-master-all.runbot216.odoo.com on model account.report on 2026-02-11 12:50:03 GMT

Traceback (most recent call last):
  File "/data/build/odoo/odoo/http/requestlib.py", line 632, in _serve_db
    return retrying(serve_func, env=self.env)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/http/retrying.py", line 52, in retrying
    result = func()
             ^^^^^^
  File "/data/build/odoo/odoo/http/requestlib.py", line 687, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/http/dispatcher.py", line 308, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/addons/base/models/ir_http.py", line 374, in _dispatch
    result = endpoint(**request.params)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/http/routing_map.py", line 207, in route_wrapper
    result = endpoint(self, *args, **params_ok)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/addons/web/controllers/dataset.py", line 32, in call_kw
    return call_kw(request.env[model], method, args, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/odoo/odoo/service/model.py", line 57, in call_kw
    result = method(recs, *args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/enterprise/account_reports/models/account_report.py", line 2825, in dispatch_report_action
    return report_to_call.dispatch_report_action(options, action, action_param=action_param, on_sections_source=False)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/enterprise/account_reports/models/account_report.py", line 2836, in dispatch_report_action
    return report_method(model, *args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/enterprise/l10n_uk_reports/models/account_financial_report.py", line 30, in send_hmrc
    self.env['l10n_uk.vat.obligation'].import_vat_obligations(self.env.context['client_data'])
  File "/data/build/enterprise/l10n_uk_reports/models/hmrc_vat_obligation.py", line 124, in import_vat_obligations
    self._get_vat(),
    ^^^^^^^^^^^^^^^
  File "/data/build/enterprise/l10n_uk_reports/models/hmrc_vat_obligation.py", line 111, in _get_vat
    if vat.startswith(('GB', 'XI')):
       ^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'startswith'

The above server error caused the following client error:
RPC_ERROR: Odoo Server Error
    RPC_ERROR
        at makeErrorFromResponse (https://100710704-master-all.runbot216.odoo.com/web/assets/0a37914/web.assets_web.min.js:3225:165)
        at XMLHttpRequest.<anonymous> (https://100710704-master-all.runbot216.odoo.com/web/assets/0a37914/web.assets_web.min.js:3231:13)
```

</p>
</details> 

Reason:
- No VAT set on the current company.

Solution:
- Blocking level error for the user to set VAT on the current company.

Task-5929908

Forward-Port-Of: odoo/enterprise#107150

**Steps to reproduce:**
* Install  `stock` module.
* Go to the > Settings*, enable *Packages* and
  *Storage Locations*(warehouse).
* Create a storable product and set *Tracking Inventory* to
  **By Quantity** and set some *barcode*
* Update the on-hand quantity for the product and assign it to one packages.
* Open *Barcode > Operations > Internal Transfer* and create a new
  transfer.
* Click the *gear icon* in the top-right corner to open the barcode
  scanning flow.
* manually enter the created product barcode and apply it.
* Click the **Back** button multiple times in quick succession.
* Go to the backend and open the created internal transfer.

**Observed behavior:**
* The internal transfer is created with *double quantities*
 compared to what was added in the barcode interface.

**Cause:**
* When clicking the *Back* button, the following flow is triggered:
  `exit()` → `beforeQuit()` → `save()`.
https://github.com/odoo/enterprise/blob/07ede9bda567d94da27da79b945e2189fa5aca6e/stock_barcode/static/src/components/main.js#L406-L414

https://github.com/odoo/enterprise/blob/07ede9bda567d94da27da79b945e2189fa5aca6e/stock_barcode/static/src/models/barcode_model.js#L473-L475

https://github.com/odoo/enterprise/blob/07ede9bda567d94da27da79b945e2189fa5aca6e/stock_barcode/static/src/models/barcode_picking_model.js#L828-L832

https://github.com/odoo/enterprise/blob/07ede9bda567d94da27da79b945e2189fa5aca6e/stock_barcode/static/src/models/barcode_model.js#L477-L483
* If the button is clicked multiple times rapidly, `exit()` is called
  again before the previous `save()` RPC completes.
* This results in multiple `save()` calls being executed, causing
  duplicated quantities on the picking.

reference - https://github.com/odoo/enterprise/pull/103999/changes/b791239c154deb6a25f85d65ebc72e3ac53b6c74

**Fix:**

 * Prevent rapidly clicking the Back button multiple times
 does not multiply quantities.

---
opw-5375899

Forward-Port-Of: odoo/enterprise#103130

**Steps to reproduce:**
* Install the **product_unspsc** module.
* Create a product with a **UNSPSC category**.
* Create and post an invoice for this product.
* Send the invoice via **Peppol**.

**Observed behavior:**
* Peppol validation fails with error **[BR-CL-13]**: *“Item classification identifier identification scheme identifier MUST be coded using one of the UNTDID 7143 list.”*
* The XML uses `listID='UNSPSC'` in `cbc:ItemClassificationCode`.

**Cause:**
* The `listID` attribute was set to the literal string **'UNSPSC'**.
* According to the **UNCL7143** code list, the correct scheme identifier for UNSPSC is **'TST'**, not 'UNSPSC'.

**Fix:**
* Replace `listID='UNSPSC'` with `listID='TST'` when generating the commodity classification node.
* Update and extend tests to validate the correct scheme identifier.
* Same for CPV code from the documentation i's code is also changed to 'STI'.

ref: https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL7143/

opw-5948723

## Versions
17.0+

## Issue
Avataxes are not computed during express checkout leading to discrepancies between customer payments and effective price including Avalara taxes.

## Steps to reproduce
*Ensure the Stripe account has activated Google Pay* *This requires a complete Google profile on Google Chrome (with a valid payment method)*
- Setup Stripe payment method in test mode with Express Checkout;
- In the Settings, in the Accounting section:
  - Setup Avatax;
  - Set main Sales/Purchase taxes to 0.
- Create a new product with 0% selling taxes and any Avatax category;
- Activate fiscal position and enable automatic detection;
- Open a Chrome session with the Google profile:
  - Go to the shop;
  - Add the product you created to the cart;
  - Enter the cart;
  - Click the "Buy with GPay" button:
    - The amount is equal to the sales price excluding taxes.
- Go to the Sales app and open the newly created order:
  - The total amount differs from the amount paid (cf. transaction).

opw-5020793

Steps to reproduce:
- Create a storable product P1 with the following BoM:
    - Component: C1
    - Operation: OP1
- Create a draft MO for P1
- Update the BoM by adding a new component
- Go back to the MO and click "Update from BoM"

Problem:
Missing Record
Record does not exist or has been deleted.
(Record: mrp.workorder(8,), User: 2)

Clicking on `update bom` will launch a call of the `action_update_bom`
which will itself call the `_link_bom` to update the record:
https://github.com/odoo/enterprise/blob/ac3f333d97eda5c86a0813490ac6204d4ec5721f/mrp_plm/models/mrp_production.py#L73-L80
https://github.com/odoo/odoo/blob/98da30375a5ae50a77d848b838781aa7247bd362/addons/mrp/models/mrp_production.py#L2406-L2418

The function will  sets `bom_id` to False, which triggers
`_compute_workorder_ids` and `_compute_move_finished_ids`
(depends on bom_id). As the MO is in draft, related moves and
workorders are deleted.
https://github.com/odoo/odoo/blob/19.0/addons/mrp/models/mrp_production.py#L849
https://github.com/odoo/odoo/blob/19.0/addons/mrp/models/mrp_production.py#L659

After that, it will try to delete the work orders again, and
since the operation no longer exists, an error will be triggered.
https://github.com/odoo/odoo/blob/19.0/addons/mrp/models/mrp_production.py#L2586-L2587

opw-5947687

### Issue:
The pill name contains the hours when it spans over the next day for less than 3 hours but not if more than 3 hours.

### Steps to reproduce:
- Go to Planning app
- Create a shift for an employee from 3pm to 2am (over two days)
- The hours of the shift are displayed
- Modify the shift end to 3am
- The hours of the shift aren't displayed

### Cause:
Before the refactor adapting the gantt view to OWL, when a shift spanned over two days less than three hours, then the gantt view truncated the pill to display it in only one day. (see [`_snapToGrid()`](https://github.com/odoo/enterprise/blame/a16b2ef569903c0ae5803c169dbd68acd0141fe1/web_gantt/static/src/js/gantt_row.js#L1044-L1072)) The same logic was done for the computation of the pill's name in [this commit](https://github.com/odoo/enterprise/commit/98a86cbacf484646f486e4648788cfa53cc9648c).

But as the pills are no longer truncated since 17.0, the computation of pill names is faulty.

### Solution:
We remove the checks of the 3-hour margin. This also makes the variable `spanMoreThanOneDay` useless, so we delete it.

opw-5881532