Users opening barcode scanning from the Barcode app main menu or operations views now see a manual barcode dialog first instead of the camera opening immediately. This lets them type a barcode when needed, still use the camera from the dialog, and receive a clear notification if camera access is unavailable.

Before this commit, clicking on the barcode image to scan opened the camera directly.

Now it opens the manual barcode dialog where the user can enter the barcode manually or use the camera.

Users can now move eligible shared Knowledge articles directly into the shared section when those articles are shared with at least one external partner. This preserves partner access during the move, reducing friction when reorganizing shared content.

Purpose:
-
Previously, the shared section allowed dropping an article only if it was moved under another shared article or if the article being moved was already a shared root article.

With this commit, dropping an article into the shared section is permitted as long as this article is shared with at least one partner (excluding the user initiating the move and internal permissions, but including inherited permissions).

In the case where a partner had access to the moved article through access inheritance, a new member will be created for this article so that this partner keeps his read/write access on this article.

Task-3603579

The appraisal list view now includes the date each appraisal was created. This makes it easier for HR users and managers to identify when appraisal records were opened and sort or review them with more context.

In this commit create date was added to the list view of the appraisal

task-3581312

The subscription option in Sales settings has been repositioned to make the configuration page easier to navigate. This helps users find and manage subscription-related sales settings more quickly.

**Version:**

- master

**Improvement:**

The position of the subscription in the res settings (Sale configurations) has been changed for improved usability.

task-3546062

Project task progress and overlap warnings now use allocated hours instead of only start and end dates. This gives managers a clearer view of team workload across multiple projects and reduces false overload warnings, while still handling field service tasks with their specific scheduling rules.

Before this commit, the progress bar values were calculated based on the
task's start and end dates. This method proved inefficient for task
planning, as it didn't account for the possibility of a user being
assigned to multiple projects concurrently. For example, if a user had
a 40-hour work week, divided between 10 hours on Project A, 15 hours on
Project B, 5 hours on Project C, and 10 hours on Project D, the
previous system would inaccurately indicate resource overload and
potential task conflict.

With this latest update, progress bar computations are now based on the
actual allocated hours, providing a more accurate reflection of task
distribution. Additionally, if a task's end date extends beyond the
Gantt view's boundaries, the progress bar values are adjusted to
represent only the visible portion of the task, which aligns with the
percentage of the task that is actually visible.

Moreover, overlapping warning are now computed based on allocated hours
as well. The condition for a conflict is that the combined allocated
hours are larger than the workable hours of the user the planned dates.
This modification does not apply the field service tasks :

    Unlike other tasks, fsm tasks overlap in two scenarios:
        1. When the combined allocated hours of an fsm task and
            a normal task exceed the user's workable hours.
        2. When two fsm tasks have overlapping planned dates.

    Example:
        - Task A (normal) conflicts with Task B (fsm) if their combined
        hours > user's workable hours. Both have 1 conflict.
        - Introduce Task C (fsm) with no allocated hours (no conflict
        with Task A) but same time period as Task B.

        Result => Task A has 1 conflict, Task B has 2 conflicts, Task C
        has 1 conflict.

taskid:3349378

Payroll dashboard warnings can now be configured to better match each company’s needs and installed payroll features. This helps payroll teams see more relevant guidance and reduces one-size-fits-all messages on the dashboard.

The obsolete setting for choosing a down payment product has been removed because it has not been used since Odoo 16.2. Down payments now rely on the standard accounting flow, reducing configuration clutter and avoiding confusion for sales and subscription users.

Since version 16.2, the Down Payments setting became obsolete. Dead field, never used.

Odoo: https://github.com/odoo/odoo/pull/145887
Upgrade: https://github.com/odoo/upgrade/pull/5430

Task: 3618096

The appraisal app now presents readiness as a clearer status, with updated status colors and a new Ready filter. Employee avatars were removed from the appraisal view to simplify the interface and help users focus on appraisal progress.

The commit message summary is a concise and clear representation of the
changes made in the commit.

  -  Changed the color of the status.
  -  Remove the employee avatar.
  -  Converted the 'ready' banner into a state.
  -  Added a filter 'Ready'.
task - 3500932

This is a backport of https://github.com/odoo/enterprise/pull/53072 Commit that introduced the issue: https://github.com/odoo/odoo/commit/14fc7f3c923847f5e052888c2cfda0bf92316972 Issue: ====== Validating required additional fields doesn't work. Steps to reproduce the issue: ============================= - Install ecommerce - Install l10n_mx_edi_website_sale - Mark the mexican company as the company for the website - Activate automatic invoice - Log out - Go to shop and add any

This is a backport of https://github.com/odoo/enterprise/pull/53072

Commit that introduced the issue:
https://github.com/odoo/odoo/commit/14fc7f3c923847f5e052888c2cfda0bf92316972

Issue:
======
Validating required additional fields doesn't work.

Steps to reproduce the issue:
=============================
- Install ecommerce
- Install l10n_mx_edi_website_sale
- Mark the mexican company as the company for the website
- Activate automatic invoice
- Log out
- Go to shop and add any item to cart and follow the steps until
  required addional informations
- Clicking on next will disable the button and mark it as loading but
  nothing happens.

Origin of the issue:
=================================
- There was some fields missing to use `s_website_form` snippet since it uses action + (foce_action or model_name) to call post method on the path but we didn't provide any.

Solution:
=========
Override the public widge to not use the send method.

opw-3635199

Forward-Port-Of: odoo/enterprise#53727
Forward-Port-Of: odoo/enterprise#53393

Impacted Version: - 16.0 and above This commit improve below features: - Add reference field to tax report - Add total excluding VAT amount to tax report - Filter completely reconciled reversed bill on purchase tax report task-3623502 Forward-Port-Of: odoo/enterprise#53798 Forward-Port-Of: odoo/enterprise#52496

Impacted Version:

- 16.0 and above

This commit improve below features:

- Add reference field to tax report
- Add total excluding VAT amount to tax report
- Filter completely reconciled reversed bill on purchase tax report

task-3623502

Forward-Port-Of: odoo/enterprise#53798
Forward-Port-Of: odoo/enterprise#52496

Since https://github.com/odoo/enterprise/pull/38427 locked orders remain in a sale state. Nothing prevent to invoice them when they are regular order. Subscription should be invoiceable too. Before this commit, the 'done' state and after https://github.com/odoo/enterprise/pull/38427 the locked orders are not invoiceable. It was done to prevent invoicing renewed contracts. This measure would make sure that only one subscription of the hierarchy could be invoiced. taskid: 3595378 Forward-Po

Since https://github.com/odoo/enterprise/pull/38427 locked orders remain in a sale state. Nothing prevent to invoice them when they are regular order. Subscription should be invoiceable too.

Before this commit, the 'done' state and after https://github.com/odoo/enterprise/pull/38427 the locked orders are not invoiceable. It was done to prevent invoicing renewed contracts. This measure would make sure that only one subscription of the hierarchy could be invoiced.

taskid: 3595378

Forward-Port-Of: odoo/enterprise#50654

[IMP] l10n_in_reports_gstr: add buy credits button -Added buy credits button in the view which gives ease to user to directly buy l10n_in_edi IAP credits [IMP] l10n_in_reports_gstr: added connection successful notification -Whenever a user is successfully connected with l10n_in_reports_gstr it will display the user a notification of successfully being connected with Indian GST Report Related PR - https://github.com/odoo/odoo/pull/120785 Forward-Port-Of: odoo/enterprise#40806

[IMP] l10n_in_reports_gstr: add buy credits button
-Added buy credits button in the view which gives ease to user to directly buy l10n_in_edi IAP credits

[IMP] l10n_in_reports_gstr: added connection successful notification
-Whenever a user is successfully connected with l10n_in_reports_gstr it will display the user a notification of successfully being  connected with Indian GST Report

Related PR - https://github.com/odoo/odoo/pull/120785

Forward-Port-Of: odoo/enterprise#40806