Helpdesk permissions were updated to match the renamed canned response feature, formerly known as shortcodes. This keeps access rules and live chat helpdesk behavior aligned with the new naming, reducing confusion for support teams.

The pull request updates internal activity property names used by the Sign and VoIP apps to align with broader platform naming changes. This helps keep activity displays consistent and maintainable without introducing noticeable workflow changes for users.

https://github.com/odoo/odoo/pull/152303

The attendance Gantt view now shows hour values with the same precision as the left-side column. This reduces confusion for users by making attendance durations consistent across the screen.

For customer, it was confusing to have a difference between hours displayed on the left colum and in the gantt view

task : 3695852

Replace `this.env._t()` (not supported in 17.0) by `_t()`. Forward-Port-Of: odoo/enterprise#55930

Replace `this.env._t()` (not supported in 17.0) by `_t()`.

Forward-Port-Of: odoo/enterprise#55930

- master - 17.0 Steps to reproduce: - Open Field Service / HR Employee Application - Open any task / employee record - Click on call button in mobile or phone field Issue: - Throws out a validation error to the user saying the mobile number which is a required field is not set Cause: - The Phone Widget Activity Patch which supplies the value of phone number from the field in which the call button has been presses has an issue - It gathers the field name in which phone widge

- master
- 17.0

Steps to reproduce:

- Open Field Service / HR Employee Application
- Open any task / employee record
- Click on call button in mobile or phone field

Issue:

- Throws out a validation error to the user saying the mobile number which is a required field is not set

Cause:

- The Phone Widget Activity Patch which supplies the value of phone number from the field in which the call button has been presses has an issue
- It gathers the field name in which phone widget is present and matches it to mobile or phone and returns either of the values

Solution:

- The simple solution is to supply the mobile number based on the field it is clicked rather than a fixed setup of supplying only mobile or phone values.

task-3678808

Forward-Port-Of: odoo/enterprise#54484

Issue: Aba is meant for batch payments and raising `UserErrors` individually for each employee/vendor prevents User from knowing all the faulty accounts. At the same time, difficult to find bank accounts for partners with multiple accounts. Fix: Raise a `RedirectWarning` with tree view to show all faulty partners/vendors simultaneously. And makes it simpler to directly find the account without the need to discard/recreate the faulty payments. 3635231 Forward-Port-Of: odoo/enterprise#554

Issue:
Aba is meant for batch payments and raising `UserErrors` individually for each employee/vendor prevents User from knowing all the faulty accounts. At the same time, difficult to find bank accounts for partners with multiple accounts.

Fix:
Raise a `RedirectWarning` with tree view to show all faulty partners/vendors simultaneously. And makes it simpler to directly find the account without the need to discard/recreate the faulty payments.

3635231

Forward-Port-Of: odoo/enterprise#55403

This PR hides the 'time_resource' option for appointment schedule-based on staff users as it is the same as the 'resource_time' option. Task-3584478 Forward-Port-Of: odoo/enterprise#56058 Forward-Port-Of: odoo/enterprise#55314

This PR hides the 'time_resource' option for appointment schedule-based on staff users 
as it is the same as the 'resource_time' option.

Task-3584478

Forward-Port-Of: odoo/enterprise#56058
Forward-Port-Of: odoo/enterprise#55314

Issue: ------ When we uninstall the `hr_referral` module, an error occurs when we want to create a job application. This is because a domain which uses a field which only exists if the `hr_referral` module is installed is persistent on window actions. It is therefore necessary to remove these domains during uninstallation, as they are no longer present on the `hr.applicant` model. opw-3708569 Forward-Port-Of: odoo/enterprise#55935

Issue:
------
When we uninstall the `hr_referral` module, an error occurs when we want to create a job application.

This is because a domain which uses a field which only exists if the `hr_referral` module is installed is persistent on window actions.

It is therefore necessary to remove these domains during uninstallation, as they are no longer present on the `hr.applicant` model.

opw-3708569

Forward-Port-Of: odoo/enterprise#55935

Fix the issue when the number of contract displayed on the contract smart button is greater than 1. Forward-Port-Of: odoo/enterprise#56036

Fix the issue when the number of contract displayed on the contract smart button is greater than 1.

Forward-Port-Of: odoo/enterprise#56036

Now the user can scan the QR code on e-invoiced vendor bills, which allows user the following functionalities: -create a new vendor bill and also will create the partner if not found with help of the data received from qr code and partner autocomplete Functional Steps: - install l10n_in_qr_code_bill_scan - Go to Account app > Vendors > Bills - Go to tree/kanban view - Click on Scan button - Scan E-invoice QR Code task-3626437 Forward-Port-Of: odoo/enterprise#54899

Now the user can scan the QR code on e-invoiced vendor bills, which
 allows user the following functionalities:
  -create a new vendor bill and also will create the partner if not found with help of the data received from qr code and partner autocomplete

Functional Steps:
  - install l10n_in_qr_code_bill_scan
  - Go to Account app > Vendors > Bills
  - Go to tree/kanban view
  - Click on Scan button
  - Scan E-invoice QR Code

task-3626437

Forward-Port-Of: odoo/enterprise#54899

Before this commit, the timesheet to validate could be not found when the filtered is made inside `action_validate_timesheet` method, it is for that reason the timesheet created inside the test is not validated as expected. This commit ensures the timesheet created is recorded yesterday to be sure the timesheet will be validated inside `action_validate_timesheet` method. runbot-56444 Forward-Port-Of: odoo/enterprise#55924

Before this commit, the timesheet to validate could be not found when the filtered is made inside `action_validate_timesheet` method, it is for that reason the timesheet created inside the test is not validated as expected.

This commit ensures the timesheet created is recorded yesterday to be sure the timesheet will be validated inside `action_validate_timesheet` method.

runbot-56444

Forward-Port-Of: odoo/enterprise#55924

### Steps to reproduce: - Install **Subscriptions** app - Open **Subscriptions** app and go to **Configuration** > **Automation Rules** - Create a **New** Rule - Under **ACTION** section, choose: - **Action To Do:** Send an email to the customer - **Email Template:** Subscription: Rating Request -for example- - Click on save button - U can notice how the **Email Template** field is empty ### Investigation: - We'll examine the case for `Send an email to the customer action`

### Steps to reproduce:
- Install **Subscriptions** app
- Open **Subscriptions** app and go to **Configuration** > **Automation Rules**
- Create a **New** Rule
- Under **ACTION** section, choose: 
    - **Action To Do:** Send an email to the customer 
    - **Email Template:** Subscription: Rating Request -for example-
- Click on save button
- U can notice how the **Email Template** field is empty

### Investigation:
- We'll examine the case for `Send an email to the customer action` but it's the same for `Send an SMS Text Message to the customer` and `Create next activity`
- The **SaleOrderAlert** model has `action_id` https://github.com/odoo/enterprise/blob/b4568ac28aaeb330eb7d679eb9ccd5afd0d78e1a/sale_subscription/models/sale_order_alert.py#L32
- It also has a non-readonly related field `template_id` https://github.com/odoo/enterprise/blob/b4568ac28aaeb330eb7d679eb9ccd5afd0d78e1a/sale_subscription/models/sale_order_alert.py#L34
- On saving the rule, we create an action https://github.com/odoo/enterprise/blob/b4568ac28aaeb330eb7d679eb9ccd5afd0d78e1a/sale_subscription/models/sale_order_alert.py#L244
- on which we set the `action_id` https://github.com/odoo/enterprise/blob/b4568ac28aaeb330eb7d679eb9ccd5afd0d78e1a/sale_subscription/models/sale_order_alert.py#L193
- but this new action doesn't have the chosen `template_id` set, and so the **_related_** `template_id` being a related field is changed to an empty record.

### Discussion
This PR extends upon https://github.com/odoo/enterprise/pull/53442 where it addresses the `next_activity` case

opw-3667217

Forward-Port-Of: odoo/enterprise#53715

In this commit we add a sound notification for incoming orders. Task: 3705003 https://github.com/odoo/odoo/pull/152323 Forward-Port-Of: odoo/enterprise#55890 Forward-Port-Of: odoo/enterprise#55700

In this commit we add a sound notification for incoming orders.

Task: 3705003
https://github.com/odoo/odoo/pull/152323

Forward-Port-Of: odoo/enterprise#55890
Forward-Port-Of: odoo/enterprise#55700

This PR addresses two issues in the account_followup module: 1. Corrected the email_from value in emails sent for automatic follow-ups. 2. Fixed the incorrect author attribution displayed in follow-up chatter, accurately reflecting the user who initiated the action. Each commit resolves a specific issue. Forward-Port-Of: odoo/enterprise#55696 Forward-Port-Of: odoo/enterprise#55376

This PR addresses two issues in the account_followup module:

1. Corrected the email_from value in emails sent for automatic follow-ups.
2. Fixed the incorrect author attribution displayed in follow-up chatter, accurately reflecting the user who initiated the action.

Each commit resolves a specific issue.

Forward-Port-Of: odoo/enterprise#55696
Forward-Port-Of: odoo/enterprise#55376

The payroll module's dashboard test was failing when the sign module wasn't installed, even though payroll doesn't require sign. This fix adds a check to only create sign-related test data when the sign module is actually available, ensuring tests run reliably regardless of which modules are installed.

Before this commit, the `test_dashboard_ui` test
in payroll was relying on sign.
However, `hr_payroll` does not depend on sign,
which would lead to the test breaking when that
module is not installed.

This commit adds a check to see if sign is installed before creating the additional data related to it.

Forward-Port-Of: odoo/enterprise#56051

This pull request records the Contributor License Agreement (CLA) signature for MohdAlmosawy, a contributor to the Odoo project. This is a standard legal requirement that allows the contributor to submit code to the Odoo repository. The change simply adds documentation confirming that the contributor has signed the necessary legal agreement.

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