This update improves performance in timesheet, project, and sales-related calculations by avoiding unnecessary sorting when grouping records. Business users should see faster loading or recalculation in affected sales timesheet and project workflows, with no intended change to visible behavior.

In this commit improve the following performance

-  replace read_group to _read_group because we don't need the order in
   compute methods.

-  read_group uses orderby which was sorting the records of groupby

-  by replacing read_group to _read_group will help us in performance by
    getting recorded faster than earlier

task-3149468

When a lead is enriched and its details are later updated, Odoo will send feedback to improve the shared company directory. This helps keep company records more accurate over time, improving future lead enrichment results for users.

Description of the issue/feature this PR addresses:
After the 'Enrich' button is used on a lead, any change to the lead information will send a vote to iap-directory. The votes will be used to improve the accuracy of the company record .

Needs this PR in order to work: https://github.com/odoo/iap-apps/pull/374


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

Odoo's AsiaPay integration now lets businesses choose the correct AsiaPay brand for their merchant account, such as PesoPay for the Philippines, SiamPay for Thailand, or BimoPay for Indonesia. This helps merchants in those countries connect to the required local payment endpoint instead of being limited to PayDollar.

Issue:

Merchant account created inside Philippine will use PesoPay, created inside Thailand will use SiamPay, and created inside Indonesia will use BimoPay. Currently. only PayDollar is available.

Cause:

Missing PesoPay, SiamPay and BimoPay.

Solution:

Add a brand setting on payment provider to allow user to select which branch will be used.

More:

- What is PayDollar, PesoPay, etc. to AsiaPay? PayDollar, PesoPay, SiamPay, BimoPay is the same system under AsiaPay but is for different countries to apply.
PesoPay is for the PH market
SiamPay is for the TH market
BimoPay is for the ID market
while PayDollar is for all other market likes HK, CN, MO, TW, SG, MY, IN, VN, NZ and AU

- Why are there multiple endpoints for a given API? Below reasons are from AsiaPay side
Local regulators requirements for BimoPay
Branding purposes to localize for the users for PesoPay and SiamPay.

- Why didn't we integrate all these endpoints in the first version of our AsiaPay implementation?
We got in touch with AsiaPay after our first integration. Therefore after partnership established with AsiaPay, they provide more integration guides on the whole development

- If many customers ask for these endpoints? Right now, there is no customers asking for these endpoints. However if they register AsiaPay under certain countries, they have to use the other endpoints otherwise they will not able to use AsiaPay on Odoo at all.

task-3073748

See also:

- https://github.com/odoo/odoo/pull/108342 (deleted by mistake)
- https://github.com/odoo/odoo/pull/108971 (targeting 16.0 but need to target master)

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

Odoo’s email composer is being updated to make message content, recipients, and templates behave more predictably. Notifications now handle attachments more consistently, and related preview, wording, and test coverage improvements reduce errors in email-based workflows.

This update improves performance in several service, planning, timesheet, quality, and sales-related areas by using a faster way to calculate grouped information when sorting is unnecessary. Business users may notice quicker loading or calculation times in related views and reports, with no intended change to functionality.

In this commit improve the following performance

-  replace read_group to _read_group because we don't need the order in
   compute methods.

-  read_group uses orderby which was sorting the records of groupby

-  by replacing read_group to _read_group will help us in performance by
    getting recorded faster than earlier

task-3149468

Several HR reporting screens now open directly in graph view, making trends easier to see without extra clicks. Employees Analysis adds an employee count measure, Appraisal Analysis defaults to a yearly Gantt view, and Recruitment Analysis is grouped by creation date for clearer activity tracking.

1) We show first graph view instead of pivot view in below report.

    -Employees Referral Analysis
    -Time In Stage Analysis
    -Payroll Analysis
    -Employees Analysis
 2) Add employee count measure in Employees Analysis report
 3) set the default year mode in Gantt of Appraisal Analysis
 4)  Improve Recruitment Analysis report
                 Currently in the graph view of the hr recruitment report, the horizontal axis is based on source.we base it
         on create instead of source.

task: 3014453