This update resolves a technical issue where the VAT field on partner records was incorrectly overriding the autocomplete feature. The fix reorganizes the display of VAT information, ensuring the autocomplete functionality now works as expected. This improves the accuracy of VAT data entry.

The xpath used in the res_partner_view replaces the vat field with a div, containing the partner vat and the VIES valid field (such that they are displayed on a single row). This results in the partner-autocomplete being removed from the field.

The solution is to make a div, and a subsequent xpath that moves the "vat" field into this div (alongside the vies valid field). This no longer overrides the partner-autocomplete xpath.

task-id: none

Forward-Port-Of: odoo/odoo#154506
Forward-Port-Of: odoo/odoo#138528

This update enhances the way contract dates are filtered within the HR system. Previously, users could only filter by month, quarter, or year, which has now been expanded to include more granular date selection options. This improves the efficiency and accuracy of contract management.

This will add options for month, quarters and year selection to the start and end dates filters.

Task: 3725209

Forward-Port-Of: odoo/odoo#152905

This update resolves a bug where the comparison price (strikethrough) remained visible on the website even after disabling the setting in the database. The fix ensures the strikethrough price only appears when the comparison price setting is actively enabled, improving website consistency.

**Current behavior:**
Enabling the 'Comparison Price' setting and filling out the field will result in this strikethrough price appearing even after disabling the setting.

**Expected behavior:**
The strikethrough comparison price will only appear when the corresponding setting is enabled in the database settings.

**Steps to reproduce:**
1. Enable the 'Comparison Price' setting in website settings

2. Select a product on the 'Shop' page of the website and edit it so it has a comparison price != to its regular one

3. Save product changes, go back to the db settings and disable the 'Comparison Price' setting

4. Go back to the website 'Shop' page and observe that the strikethrough comparison price is still displayed

**Cause of the issue:**
In the product.template model in website_sale, the price values are modified to those informed by the compare_list_price value independent of the current value of the corresponding database setting. It only checks if there is non-False value in the field.

**Fix:**
Look at the 'Comparison Price' setting before the price modification/calculations take place and skip them if it's False.

opw-3705079

Forward-Port-Of: odoo/odoo#154274
Forward-Port-Of: odoo/odoo#151734

This update resolves an issue where custom attributes weren't consistently applied when closing product configuration forms. The team has reverted a specific workaround and now uses standard Odoo methods for configuration updates, ensuring all custom attributes are correctly saved and applied. This improves the reliability of product configuration workflows.

Updates to existing product configurations with custom attributes were not correctly applied on configurator closure.

This was probably caused by a recent update in the framework. Nevertheless, to solve the problem, this commit drops the use of custom code used only by the configurator to stick to the standard usage of magic commands.

Fixes #152647

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

Forward-Port-Of: odoo/odoo#152934