This update improves day-to-day accounting and expense workflows by hiding empty dashboard lines, adding easier access to expense reports, and making printed invoice notes clearer. These changes help users find relevant information faster and produce cleaner customer-facing documents.

Task 2176461
* Dashboard: don't show lins if there is no data
* Add new menu for expense reports
* Reorganize notes on bottom of printed invoice

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

Timesheet reports have been refined to make the information easier to read and analyze. Graph measure labels now better reflect the intended business wording, improving clarity for users reviewing time, attendance, and sales-related timesheet data.

Some small improvements in timesheet report view.
In measures of graph, take string attribute into account.

TaskID: 2149371


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

Updates help text on employee work information fields to better explain who is responsible for coaching, time off approvals, and expense approvals. This helps HR users understand what each responsible person field means and what happens when no approver is set.

Task : https://www.odoo.com/web#id=2168330&action=327&model=project.task&view_type=form&menu_id=4720

Pad: https://pad.odoo.com/p/r.a8dff92edca2e7c537e89e03eb5dce09

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 prepares Odoo Events to support ticket management without requiring the eCommerce sales flow. It also cleans event setup data, improves ticket-related views and tests, and fixes event scheduling and seat limit editing issues.

PURPOSE

Integration between event and eCommerce is required only when users handle the
entire selling process online. However users may require ticketing support
while managing payments outside of Odoo. Purpose of this commit is to prepare
support of tickets directly in event application without need of sales.

SPECIFICATIONS

Clean existing event type demo and data

Clean fields definition and parameters (no functional or technical
changes, just cleaning their definition).

Add tests before updating models. As some event models (event.type and
event.ticket notably) are about to be modified let us add some tests to avoid
regressions. Security tests are also moved in their own file. Some internals
tests defined in event_sale are also moved in their own file. That way we
avoid bloating files with unrelated tests. Future commits will add tests for
event and event.type models.

Prepare views for ticket model update :


  * define views for ticket model. Currently views are directly embedded
    in o2m of event.type and event.event, leading to complex xpath to
    modify them. They are now real views;
  * split templates in website_event_sale, to have templates related to
    website_event and website_sale separated, leading to more simple diff
    comprehension;

Add some fixes :

  * copy event type mail scheduling only if activated on event type;
  fix seats_max field not editable;

See sub commits for more details.

LINKS

Task ID 2177281 (support tickets directly in event)
Prepares Community PR #43488
Closes Community PR #44066

The sales invoice creation wizard now has unique identifiers on key buttons and sections. This makes future customizations safer and easier by avoiding fragile references to duplicate or unnamed screen elements.

Description of the issue/feature this PR addresses: Set unique ID's on button and div elements.

Current behavior before PR:
1. Before this commit there were two buttons on this wizard with the same name 'create_invoices' that do different things. One creates the invoice and the other one creates and opens the invoices.
2. Before the commit there are two divs without an ID. 

Desired behavior after PR is merged:
1. By setting an unique ID on both buttons we can do a clean and easy xpath. Something like `<xpath expr="//button[@id='create_invoice_open']" position="replace"/>` instead of having to use indexes or dangerous behaviours
2. By setting an ID on the divs we can easily xpath by name.


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

Event teams can now manage sponsors more like business contacts, with better views and built-in communication and activity tracking. Attendee handling is also easier through batch updates, improved event lists, better website sale registration links, plus small fixes for mailing defaults and empty phone or email display.

Purpose
=======

Improve the sponsors and attendees integration in event. Focus on :

  * sponsor management: transform it into a real business document allowing
    to communicate with sponsors) ;
  * attendee management: improve views, ease searching / updating them in
    batch;

Specifications
==============

Sponsors
--------

Move all the views related to sponsor and sponsor type to their own file to
clean module organization.

Add integration with mailgateway and activities through mail.thread and
mail.activity.mixin inheritance.

Improve sponsor views: add a real form view and add a small kanban view
displaying some partner / sponsor information.

Attendees
---------

In order to allow state management in batch, state field is made editable in
multi edit mode of registrations. That way event managers are able to work in
batch. It required to move some code currently called in custom action-called
methods directly in write. It makes sense to consider that some required code
is called by writing on state field instead of depending on calling the right
method. Indeed there is not much "business" code to move: calling mail
schedulers on confirmation, and putting the closing date when closing.

Event and registration tree views are improved, some fields are now editable
in multi edit mode.

When a user register on a event from website, it will create a sale order and
a partner (the customer of the SO). Set automatically the partner of the
registration to the partner of the sale order.

Other
-----

This merge include a fix in mass mailing (default domain propagation) and
web (void values display for phone widget). See sub commits for more details.

Task ID 2119333
PR #40949

Pivot table exports now download as XLSX files instead of older XLS files, allowing much larger spreadsheets with more rows and columns. The export also consistently includes the measure row, making downloaded reports clearer even when only one measure is selected.

Task:https://www.odoo.com/web#id=2127388&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720

Pad: https://pad.odoo.com/p/r.4fde01e8f05ca7b57c03c22600d70e41



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

The event kanban card layout was adjusted to make room for additional footer information, such as social media statistics. This keeps event cards visually consistent while enabling clearer reporting in related integrations.

Purpose
=======
In "Event social Facebook", we want to insert some statistics
in the footer of the kanban card.

So, we added a div element, to be able to add the fotter bellow
the card.

Adjust the CSS to keep the same view.

Task #1999230

Several business areas now use a simpler and more reliable way to interpret saved filter criteria and domains. This is an internal improvement that should help maintain consistency across reports, imports, subscriptions, planning, marketing automation, and social notifications without changing day-to-day workflows.

To evaluate a domain, it is easier to use ast

Goes with odoo/odoo#43831

This update makes several small accounting workflows clearer and easier to use. Users can better distinguish debits and credits during batch payment reconciliation, see clearer wording for deferred revenue actions, and preview PDFs while navigating journal items with the keyboard.

Task 2176461
* Differentiate debit/credit in reconciliation of batch payments
* Change label of button for deferred revenues
* Show pdf on keyboard nav in journal items list views

The help text for the Timesheet responsible field on employee work information was updated to better explain who approves an employee's timesheets. This helps HR and managers understand what happens when no specific approver is assigned.

Task :https://www.odoo.com/web#id=2168330&action=327&model=project.task&view_type=form&menu_id=4720

Pad :https://pad.odoo.com/p/r.a8dff92edca2e7c537e89e03eb5dce09

Managers can now choose which employees receive a published planning schedule and narrow the shifts being sent by role, project, or task. Shift templates can also include project and task details, helping teams prepare more relevant schedules with clearer context.

Improve the publish and send action: we can choose which employee will received this
planning, we can filter slot by role, project or/and task.

Add task and project on shift templates.

TaskID: 2146842

Timesheet grid entries with very long name segments are now shortened, making the grid easier to read and navigate. Timesheet report views were also improved to provide clearer reporting for business users.

In grid view, if the length of a block of the name line, is longer
than 50 characters, we reduce it.
Improve timesheet report views.

TaskID: 2149371

Planning managers can now choose exactly which employees receive published schedules and filter shifts by role, project, or task before sending. Shift templates now include project and task details, and schedule dates and times better respect each user's language preferences.

Improve the publish and send action: we can choose which employee will received this
planning, we can filter slot by role, project or/and task.

Improve front-end: take into account langage preferences to display date and time.

Add task and project on shift templates.
TaskID: 2146842

Sales teams can now be automatically prompted to take manual follow-up actions when customer invoices become overdue. This helps ensure unpaid invoices are noticed sooner and followed up by the right salesperson.

Today, there is nothing that reminds a salesperson that an invoice
becomes overdue. By allowing to create a manual activity in the followup
models, one can remind the sale person than an invoice has not yet been
paid.