Users can now type simple shortcuts in date and date-time fields, such as adding days, weeks, months, or years from today. This makes entering common relative dates quicker and reduces manual calendar navigation.

This commit adds smart date inputs for date and datetime fields.

The goal of smart date input is to provide the user some shortcuts
when setting dates.

The rule is [+-]\d+[dwmy]?
So we can enter inputs like:
  +3  to have today + 3 days
  -2w to have today - 2 weeks
  +1y to have today + 1 year
  +5m to have today + 5 months
  -4d to have today - 4 days

Task: 2270347

Website editors can now add parallax motion and color overlays to any snippet that uses a background image, not just selected sections. This gives business users more design flexibility, including control over parallax direction and intensity, while preserving reusable images without permanently altering them.

Enable the parallax option for all snippets with a background image.

task-46147

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

Manufacturing orders now include service-type items from the bill of materials when calculating valuation. This gives businesses a more complete view of production costs and improves the data available in cost analysis reports.

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

This update reduces unnecessary database work across customer portal pages, making common pages like account details, invoices, orders, projects, and timesheets load faster. It also keeps an empty opportunities section hidden, matching the behavior of other portal sections.

##### Perf improvements
* `portal, *`: Do not compute home portal record counts when on a specific page (not needed)
*  `hr_timesheet`: Domain simplification
* `website`: Avoid `ref` queries on website frontend templates
* `portal`: Avoid multiple calls to same function in `/my/account` qweb template

##### minor functional change to verify
* `website_crm_lead_partner_assign`: do not show opportunities section if empty (like all other sections).

### Performance gains:

Basic db with demo datas, page accessed as admin user.

| Portal page\Queries | Before | After | Module                     |
|---------------------|--------|-------|----------------------------|
| _/my, /my/home_       | 70     | 60    | `portal`                     |
| _/my/account_         | 84     | 38    | `portal`                     |
| _/my/timesheets_      | 96     | 54    | `hr_timesheet`               |
| _/my/projects_        | 74     | 36    | `project`                    |
| _/my/tasks_           | 77     | 39    | `project`                    |
| _/my/invoices_        | 72     | 34    | `account`                    |
| _/my/purchase_        | 72     | 34    | `purchase`                   |
| _/my/orders_          | 81     | 43    | `sale`                       |
| _/my/quotes_          | 81     | 43    | `sale`                       |
| _/my/tickets_         | 72     | 34    | `helpdesk`                   |
| _/my/leads_          | 73     | 35    | `website_crm_partner_assign` |
| _/my/opportunities_   | 73     | 35    | `website_crm_partner_assign` |

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

Sample data now avoids showing every next activity as a warning. This makes demo and test screens look more realistic and easier for users to understand.

The SampleServer picks a random value for selection fields. As a
consequence, field 'activity_exception_decoration' is always set,
either to 'warning' or 'danger'. This means that the next activity
field always displays "Warning" (it displays the next activity only
if this field is not set).

This special case has been handled in web, as it is the first (and
only) one. In the future, if we have to implement several special
cases like that, we'll setup a proper hook to allow external
modules to define them from the outside.

Task 2316726

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

Reporting screens now show realistic sample data and clearer helper messages when users have not yet entered records. This makes empty dashboards, graphs, pivots, and related views easier to understand and helps new users discover what to do next.

The present commit allows to display sample data in the reporting views and effectively
enable them in several graph views. Moreover, many action helpers have been added
across all applications. With this, we hope to facilitate the onboarding of the new users.

Task IDs: 2282196, 2311486

Co-authored-by: Mahendrasinh Barad <mba@odoo.com>
Co-authored-by: Aaron Bohy <aab@odoo.com>
Co-authored-by: Mathieu Duckerts-Antoine <dam@odoo.com>

Archived eLearning courses now keep their lesson list visible to internal users while ensuring the lessons are unpublished and not publicly accessible. This makes archived course management more consistent and prevents empty course pages when reviewing past content.

Archived courses had empty content list (because they where archived too).
Unpublish the content (slide) if course is archived to be consistant.

Continuity/IMP of task-2170708
Task-2225598

Old pull request : https://github.com/odoo/odoo/pull/50368

Customers can now change their language directly in the portal even when the Website app is not installed. This makes portal pages easier to use for multilingual users and reduces reliance on website-specific features.

Make the language switcher available on portal without website installed

task-2203383

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

This update improves the day-to-day experience in Odoo Accounting, especially around journal configuration and related forms. It also refines the bank account creation wizard, making setup smoother and reducing friction for accounting users.

Miscellaneous changes aiming to improve the user experience in the accounting module,
mainly in the journal model and its form view.

Task ID: #2250349
Pr : [11862](https://github.com/odoo/enterprise/pull/11862)

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

This update improves how website-related features check whether optional views are enabled, avoiding reliance on cached lookups. It helps event, membership, shop comparison, wishlist, and e-learning pages reflect configuration changes more accurately for users.

Use is_view_active instead of viewref which one is cached.

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

Expense report payments now use the standard accounting payment process, making it easier to pay several entries at once and group payments. Expense sheets also show payment details and remaining amounts directly on the form, while a duplicate expense check module is removed.

…wizard

- Use the one defined in the account module allowing paying multiple journal entries
and group payments together.
- Improve the usability to track the residual amount in an expense sheet by adding the
payment details & the residual amount in the form view instead of using the chatter.
- Remove the hr_expense_check module that contains only duplicated features regarding the
register payment wizard.

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

Reporting and dashboard screens across several business apps now show sample data when there are no real records yet. This makes empty reports more understandable and helps users see what insights will be available once they start using the app.

Task ID: 2282196

Customer portal pages now avoid unnecessary record counting and database checks, especially when users are already viewing a specific page. This improves loading speed across portal areas such as Helpdesk, Subscriptions, Sign, and Website without changing the user-facing workflow.

* Do not compute home portal counts when on a specific page
* `helpdesk`: Avoid searching on models when a count is enough.
* `website_enterprise`: Avoid ref calls in website templates.
* semantic changes for more consistent portal methods

Enterprise counterpart of odoo/odoo#52934

This update improves the accounting experience, especially around journals and related accounting workflows. It also includes smaller refinements across reporting, bank statement imports, payroll accounting, subscriptions, and localization areas to make daily finance operations smoother.

Miscellaneous changes aiming to improve the user experience in the accounting module,
mainly in the journal model and its form view.

Task ID: #2250349
Pr : [54494](https://github.com/odoo/odoo/pull/54494)

Projects can now create recurring tasks for regular interventions such as fire alarm maintenance or safety inspections. This helps teams avoid missed follow-ups and reduces manual scheduling work.

Some interventions are done on a regular basis (e.g. maintenance of
fire alarms, safety inspections). Having tasks auto-generate would
facilitate the process and would ensure that the next intervention
isn't missed/forgotten.

TaskID: 2172156

This fix ensures Odoo's main workflow tests start with the required make-to-order inventory route enabled, so the test scenario matches how the flow is meant to work. It also corrects a small issue where route options could be hidden when opening a product form from a create/edit action.

Enable MTO route at the start of main flow tour since it's used
by it. Also fix a small bug when the form view is open from a
create edit where the route are hidden.

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

New accounting sequences now use the configured starting number or the last known number instead of restarting from zero. This prevents electronic invoices from being assigned duplicate or invalid numbers, helping businesses validate invoices with external tax authorities such as AFIP.

task 355
---

### Description of the error

Use last or starting sequence for new sequences instead of setting the seq to 0 all the time. Useful when we set the starting sequence for electronic invoices using webservices. Here is an example of how to reproduce it for AR localization:

1. Create a new journal for electronic invoice with this data ![image](https://user-images.githubusercontent.com/7593953/89950899-dcc17c80-dc00-11ea-83f1-42cba6c8a170.png)
2. Go to menu "Accounting / Accounting / Actions / Consult invoice in AFIP" and get the information of the last invoice "FACTURA (A)". At the moment this ticket was reported the next number was 42  ![image](https://user-images.githubusercontent.com/7593953/89950999-067aa380-dc01-11ea-8abf-6d3b00cfefda.png)
4. Create a new invoice for the Journal FE 1234 of document type "Factura (A)"

### Current behavior before the PR

Is showing that the document number is 01234-00000001 ( seq = 1)
![image](https://user-images.githubusercontent.com/7593953/89951141-3fb31380-dc01-11ea-8b8e-810687624ce1.png)

And if I try to validate the invoice we receive an error from AFIP
![image](https://user-images.githubusercontent.com/7593953/89951314-8ef94400-dc01-11ea-8b1a-e8049e0bcca4.png)


### Desired behavior after the PR

Will show that the document number is 01234-00000043 (seq) and we will be able to validate the invoice in AFIP


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

This fixes issues that could block or incorrectly mark Argentinian electronic invoices during validation. Invoices are now only treated as fully validated after both Odoo and AFIP validation succeed, reducing false validation errors for users.

task 346
---

Multiple fixes that is making the invoice validation fail, this fixes are corresponding to another massive changes made in master for Odoo team.

1. validated invoices shown validation error
![image](https://user-images.githubusercontent.com/7593953/89681446-57219200-d8cb-11ea-88ce-6f219b0b5420.png)
2. fix invalid keyword
![image](https://user-images.githubusercontent.com/7593953/89681530-80dab900-d8cb-11ea-837b-506462637cdd.png)

The payroll expense workflow now allows users in the Billing role to post and pay expense reports. This fixes an access issue so billing teams can complete expense processing without needing extra permissions or handoffs.

--task: 2273528

Manufacturing order cost reports now keep a more accurate snapshot of costs at the time inventory is posted. This prevents later changes to work center rates or bills of materials from altering historical reports, improving trust in past production costing.

WIP

Before this commit, the loading order of the search panel sections was fixed: categories first, then filters. This caused issues when the categories needed to know the current valid domain to fetch new counters because a selected filter value could have been discarded when selecting a new category. Now, the filters are fetched first when toggling a category value and this problem is avoided. Enterprise PR: https://github.com/odoo/enterprise/pull/12180 Forward-Port-Of: odoo/odoo#55385

Before this commit, the loading order of the search panel sections was
fixed: categories first, then filters. This caused issues when the
categories needed to know the current valid domain to fetch new counters
because a selected filter value could have been discarded when selecting
a new category.

Now, the filters are fetched first when toggling a category value and
this problem is avoided.

Enterprise PR: https://github.com/odoo/enterprise/pull/12180

Forward-Port-Of: odoo/odoo#55385

Before this Commit, Datetime on warning was not formatted based on User's lang. With this commit, we use `format_datetime` to correctly format Datetime. 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#51365

Before this Commit, Datetime on warning was not formatted based on User's lang.

With this commit, we use `format_datetime` to correctly format Datetime.

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#51365

Having a non paid membership for last year and being associate with someone having a non paid membership was dispalying an 'old' membership state instead if a 'non' membership. Assumption: If an associate member is added, take the state of the associate member (tooltip of associate member). In case the associate member is a 'non member', it's stupid to associate with someone that is paying or have paid as it won't consider the state of the current paid member, the link has to be made o

Having a non paid membership for last year and being associate with
someone having a non paid membership was dispalying an 'old' membership
state instead if a 'non' membership.

Assumption:
If an associate member is added, take the state of the associate member
(tooltip of associate member).
In case the associate member is a 'non member', it's stupid to associate
with someone that is paying or have paid as it won't consider the state of
the current paid member, the link has to be made on the other side:
the 'non' paying will be associate with the 'paid'.

Create membership for
        a/ 2019 (1jan to 31dec)
           > For the calculation of the 'old' state
        b/ 2020 (1jan to 31dec)
           > For the calculation of the 'paid' state

Create few res.partner:
AA: No associate.
        2019 - Paid
        2020 - Paid
        >> Paid member
        (= ok)

CC Case 1:
Associate with AA
        2019 - Invoiced (but not paid)
        2020 - None
        >> Paid member due to association with AA
        (= ok)

CC Case 2:
Not associate:
		2019 - Invoiced (but not paid)
        2020 - None
        >> Before fix: Old member
        (= nok)
        >> After fix: Non member
        (= ok) As he never paid and not linked to someone that paid.

DD: Associate with AA
        2019 - Invoiced not paid
        2020 - Paid
        >> Paid member (with or without association with AA)
        (= ok)

EE Case 1:
Not associate:
        2019 - Paid
        2020 - None
        >> Old member
        (= ok)

Case 2:
Associate with DD
        2019 - Invoiced (not paid)
        2020 - None
        >> Paid member (due to association with DD)
        (= ok)

Case 3:
Associate with CC
        2019 - Invoiced (not paid)
        2020 - None
        >> Before fix: Old member (due to none having a current 2020 invoiced)
        (= nok it should take the state of CC)
        >> After fix: Non member (as CC is not a member)

opw-2287050

Forward-Port-Of: odoo/odoo#55668
Forward-Port-Of: odoo/odoo#54840

Before this commit we cehck first if user was publisher before to check if the exception was a 404 NotFound. What's means that we make this check (1 query sql) most of the time for no reason, and worst case, when the exception crashes the cursor, this check will reraise a new exception because isPublisher check is done with a closed cursor. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I

Before this commit we cehck first if user was publisher before to check if the
exception was a 404 NotFound.

What's means that we make this check (1 query sql) most of the time for no
reason, and worst case, when the exception crashes the cursor, this check will
reraise a new exception because isPublisher check is done with a closed cursor.

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#55780

opw-2312139 The Andhra Pradesh state code change from 28 to 37 Source :https://ddvat.gov.in/docs/List%20of%20State%20Code.pdf 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#55732

opw-2312139
The Andhra Pradesh state code change from 28 to 37
Source :https://ddvat.gov.in/docs/List%20of%20State%20Code.pdf

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#55732

task-2280166 Forward-Port-Of: odoo/odoo#55723

task-2280166

Forward-Port-Of: odoo/odoo#55723

Before this commit, if you don't have the sale access right, when you arrive on main website menu, the dashboard try to load some utms data and will fail with a traceback. Now we don't render utm graph it you don't have the sale access right This commit closes odoo/odoo#54695 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/s

Before this commit, if you don't have the sale access right, when you arrive on
main website menu, the dashboard try to load some utms data and will fail with
a traceback.

Now we don't render utm graph it you don't have the sale access right

This commit closes odoo/odoo#54695

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#55785

Before this commit, the field badge could overflow from its boundaries and have part of its pill/text hidden. Now, the "overflow" mixin has been applied and the badge is properly contained. 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#55786

Before this commit, the field badge could overflow from its boundaries
and have part of its pill/text hidden.

Now, the "overflow" mixin has been applied and the badge is properly
contained.

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#55786

PURPOSE Review the tips and digest layout design to make sure they have a WOW effect and increase trial conversion/retention. SPECIFICATIONS: LAYOUT Besides changing the tips, a cleaning of digest layout was performed. Emails were reported to look not neat in Outlook and somewhat random in mail.com or gmail.com. Most recent HTML CSS cannot be used to make HTML emails because each email provider renders emails its own way. This means a given email may renders differently in gmail

PURPOSE

Review the tips and digest layout design to make sure they have a WOW effect
and increase trial conversion/retention.

SPECIFICATIONS: LAYOUT

Besides changing the tips, a cleaning of digest layout was performed. Emails
were reported to look not neat in Outlook and somewhat random in mail.com or
gmail.com.

Most recent HTML CSS cannot be used to make HTML emails because each email
provider renders emails its own way. This means a given email may renders
differently in gmail.com and outlook.

The layout of the email was composed of several levels of embedded tables
which means huge maintenance effort. So it was totally rewritten with divs
and CSS, but some properties are not taken into account.

A lot of page component improvements were done. It consisted in replacing most
of the style attribute in tags with CSS classes and ids. This step is
especially useful for tip formatting because before, if a style modification
was needed, it had to be performed on each tip individually.

SPECIFICATIONS: TIPS

Add / Improve tips in cmr, purchase, hr_recruitment, website, hr_expense, project,
digest, sale_management, im_livechat, stock, mrp, account.

LINKS

COM PR: odoo/odoo#53580
ENT PR: odoo/enterprise#11394

Forward-Port-Of: odoo/odoo#53580

- Create Tax 0: Percentage Amount: 0 Tax Included Tax Group 0 - Create Tax 8: Percentage Amount: 8 Tax Included Tax Group 8 - Create a customer invoice with one line Quantity: 8.0 Price Unit: 15.55 Taxes: Tax 8, Tax 0 (order is important) The tax amounts are: Tax 8: 9.22 Tax 0: -0.01 If the taxes are inverted, the tax amounts Tax 8: 9.21 Tax 0: 0.00 The difference is due to the rounding of the 8% tax done differently. In the second case, t

- Create Tax 0:
  Percentage
  Amount: 0
  Tax Included
  Tax Group 0
- Create Tax 8:
  Percentage
  Amount: 8
  Tax Included
  Tax Group 8
- Create a customer invoice with one line
  Quantity: 8.0
  Price Unit: 15.55
  Taxes: Tax 8, Tax 0 (order is important)

The tax amounts are:
  Tax 8: 9.22
  Tax 0: -0.01

If the taxes are inverted, the tax amounts
  Tax 8: 9.21
  Tax 0: 0.00

The difference is due to the rounding of the 8% tax done differently. In
the second case, the computation of the 8% tax goes through:

https://github.com/odoo/odoo/blob/8c5cd335a57c20ed5faa6b7c7630c296c1f2a5cf/addons/account/models/account.py#L1480

In the first case, the amount is recomputed in:

https://github.com/odoo/odoo/blob/8c5cd335a57c20ed5faa6b7c7630c296c1f2a5cf/addons/account/models/account.py#L1483

The rounding is different in both cases, leading to an inconsistency.

When the tax amount is zero, there is no need to save the amount in
`total_included_checkpoints`.

opw-2306676

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#55733
Forward-Port-Of: odoo/odoo#55572

In a French based company Create a DEMO product with price 500 available in POS Have a public pricelist in which feature a line with: - product: DEMO - minimum quantity: 1 - price: 400 Open POS, Add DEMO, the price from the pricelist will be used. Now delete the product. The form will popup, choose a quantity to delete and confirm. The price of the cancel line will not be taken from the pricelist, so the two line will have different prices. This occur because the quantity of the n

In a French based company
Create a DEMO product with price 500 available in POS
Have a public pricelist in which feature a line with:
- product: DEMO
- minimum quantity: 1
- price: 400

Open POS, Add DEMO, the price from the pricelist will be used.
Now delete the product.
The form will popup, choose a quantity to delete and confirm.

The price of the cancel line will not be taken from the pricelist,
so the two line will have different prices.
This occur because the quantity of the new line is -1 and the pricelist
may have a minimum positive quantity set.

Using a specific option to keep the price fix the issue

opw-2312172


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

Forward-Port-Of: odoo/odoo#55699
Forward-Port-Of: odoo/odoo#55680

PURPOSE Review the tips and digest layout design to make sure they have a WOW effect and increase trial conversion/retention. SPECIFICATIONS Enterprise counterpart of odoo/odoo#53580 . In this merge we add tips in the following apps: account_accountant, documents, planning. We improve helpdesk tips. Digest_enterprise module is added that holds base tips requiring enterprise features. LINKS Task ID-2274264 COM PR: odoo/odoo#53580 ENT PR: odoo/enterprise#11394 Forward-Port

PURPOSE

Review the tips and digest layout design to make sure they have a WOW effect
and increase trial conversion/retention.

SPECIFICATIONS

Enterprise counterpart of odoo/odoo#53580 . In this merge we add tips in the
following apps: account_accountant, documents, planning. We improve helpdesk
tips.

Digest_enterprise module is added that holds base tips requiring enterprise
features.

LINKS

Task ID-2274264
COM PR: odoo/odoo#53580
ENT PR: odoo/enterprise#11394

Forward-Port-Of: odoo/enterprise#11394

This commit fixes a small flicker in the twitter user search by forcing the main color on the dropdown text. Task 2250877 Forward-Port-Of: odoo/enterprise#10562

This commit fixes a small flicker in the twitter user search by forcing the
main color on the dropdown text.

Task 2250877

Forward-Port-Of: odoo/enterprise#10562

The summary email sent to the employee/applicant is missing the wage information. Add the wage in the Contract Information Forward-Port-Of: odoo/enterprise#11140

The summary email sent to the employee/applicant is missing
the wage information.

Add the wage in the Contract Information

Forward-Port-Of: odoo/enterprise#11140

Before this commit, the loading order of the search panel sections was fixed: categories first, then filters. This caused issues when the categories needed to know the current valid domain to fetch new counters because a selected filter value could have been discarded when selecting a new category. Now, the filters are fetched first when toggling a category value and this problem is avoided. A mobile test has been adapted accordingly to these changes. Community PR: https://github.c

Before this commit, the loading order of the search panel sections was
fixed: categories first, then filters. This caused issues when the
categories needed to know the current valid domain to fetch new counters
because a selected filter value could have been discarded when selecting
a new category.

Now, the filters are fetched first when toggling a category value and
this problem is avoided.

A mobile test has been adapted accordingly to these changes.

Community PR: https://github.com/odoo/odoo/pull/55385

Forward-Port-Of: odoo/enterprise#12180

Currently, When try to create contract template from Employee app setting, it show duplicate templates fields. So in this commit, Hide the duplicate template fields when create contract template from employee app setting. TaskID: 2303270 Closes: #12270 Forward-Port-Of: odoo/enterprise#12270

Currently, When try to create contract template from Employee app setting,
it show duplicate templates fields.

So in this commit, Hide the duplicate template fields when create contract
template from employee app setting.

TaskID: 2303270
Closes: #12270

Forward-Port-Of: odoo/enterprise#12270

fix bugs Task 2298950 PR #12096 Forward-Port-Of: odoo/enterprise#12096

fix bugs

Task 2298950
PR #12096

Forward-Port-Of: odoo/enterprise#12096