Gantt views no longer show placeholder sample records when there is no real data. This avoids confusing or unattractive totals and keeps attendance and planning screens focused on actual business information.

This commit removes the sample data records from gantt because it looks weird with the total row and it isn't adding much to the user experience.

task-4009082

The appointment invitation screen no longer shows shortcode warnings before an appointment type is chosen. This avoids confusing users with warnings that are not relevant yet and makes the setup flow cleaner.

Purpose
========
- Unique Shortcode warning and shortcode format warning are visible even when there is no appointment type selected which seems weird.

Specification
==============
- This commit addresses the issue now, the warning will not be there when no appointment type is selected.

Task-4437892

Users can now delete a GST return period when an error occurs while it is being sent. This helps businesses recover from failed GST filing attempts without being blocked by a stuck period.

With this PR, user can delete the GST return period if an error is received
while the status is `sending`.

task-4471668

This update tightens internal validation so new records are created using the expected data format. It helps catch developer mistakes earlier, improving reliability across accounting, appointments, and recruitment workflows without changing day-to-day user behavior.

Planning publication now includes the final day chosen in a date range. This makes scheduling more intuitive by ensuring a range such as day 1 to day 10 includes day 10 when publishing.

This commit's purpose is to add the last day selected when the 'publish' button is used since it is not intuitive to miss the day 10 when a user select a date range from day 1 to day 10

Default user access settings have been moved to configurable default groups across several Odoo apps. This helps businesses manage standard permissions more consistently when installing or using these modules.

task: 4341594

The Studio chatter area is now easier to see when users hover over it in dark mode. This improves readability and makes form editing more comfortable for users working with dark themes.

SPECIFICATION:

Improves the visibility of the chatter in dark mode when hovering in studio.

Task-4574621

Authorized users can now reset an IoT Box password directly from the connected Odoo IoT app, instead of using the device homepage. This makes the process easier to manage while relying on signed requests to ensure only approved users can perform the reset; standalone boxes can still generate a password from their homepage.

Since database-to-IoT Box network requests are now signed, we can move the ssh password reset from the IoT Box homepage to the connected database as we can now ensure that the request is performed by an authorized member.

If no database is connected, the password can still be generated from the IoT Box homepage.

Community PR: [https://github.com/odoo/odoo/pull/200550](https://github.com/odoo/odoo/pull/200550)
Task: 4383920

Appointment validation pages now show booked people or resources more consistently based on the appointment setup. This helps customers see relevant booking details, including resource pictures when applicable, while hiding unnecessary auto-assigned resource information.

Purpose
=======
Keep a display consistency for the user/resource on the validation page
and show the pictures when multiple resources are booked.

Specification
=============
When the appointment type have the "resource_manage_capacity" set to True,
it is the only configuration where multiple resources can be booked.
In this case, on the validation page, display the resources in the
form details no matter if there is one or multiple resources booked
to keep a display consistency for the appointment type.
If the avatars_display is in 'show picture', display the pictures next to
the resource names.

When the "resource_manage_capacity" is set to False (when based on users or
based on resources but we can only book one at a time), display the user or resource
on the right on the validation page (with the description and/or image if in "Show picture").
Only exception is when there is no description and the appointment type configuration
is in "No Picture", in this case to prevent displaying the user/resource name alone
on the right, displaying the user/resource in the form details.

When the config is "auto-assign" and "no picture":
- if based on resources, completely hide it from the validation page.
i.e. if a restaurant wants to auto-assign tables, no need for the user to know which one.
- if based on users, hide its details on the right of the validation page but keep them
in the form details section.
i.e. if we book an appointment with a Sale, it's important to know with who but no need to
have the floating info without pictures on the right as they already are in the form details section.

Task-4395325

Timesheet grid row titles for projects, sales order lines, and helpdesk tickets can now open the related record when the user has the right access. This makes navigation faster while keeping restricted records read-only for users without permission.

This commit enhances the timesheet grid component by making the grid row title
clickable, depending on user access rights:
- The row title 'Project' will clickable if the user has read access to that project,
 otherwise, it remains read-only.
- The row title 'Sale Order Line' will clickable for users with read access to the
 corresponding record.
- The row title 'Ticket' will clickable if the user has helpdesk user access rights.

task-3429403

Portal users can now open attachments shared in comments on Knowledge articles. This makes shared article discussions more complete for external users by ensuring they can view the related files they are meant to see.

Purpose
========
To grant access to attachments that are in the comments of knowledge articles.

Specification
================
This commit enables the portal users to view the attachment linked to the knowledge article's comments.

This update lets Odoo recognize point-of-sale categories by their full hierarchy, so products can be imported into nested POS categories without errors. It improves data import reliability for businesses using multi-level POS category structures.

Description of the issue/feature this PR addresses:
Adding new field for `_rec_name` (`complete_name`) which will be computed by hierarchy

Current behavior before PR:
Currently we cannot import product's POS category if it's nested.
Odoo will show error because the POS category is not found

Desired behavior after PR is merged:
Will be able to import nested POS category



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

Vendor bills are now checked more broadly for potential duplicates, including when dates are missing or only the same year matches. Suspected duplicates stay visible, are highlighted in list views, and prevent automatic posting so teams can review them before payment or accounting actions proceed.

See commits :)

Entreprise PR: https://github.com/odoo/enterprise/pull/79471

Mexican localization now recognizes received vendor bills when checking SAT status, so users can see the SAT validation field on vendor bill forms. This brings vendor bill visibility closer to the existing invoice workflow and helps accounting teams verify compliance status more easily.

Adding 'invoice_received' as an accepted state in l10n_mx_edi_document.py -> _update_document_sat_state and account_move.py -> _compute_l10n_mx_edi_cfdi_state_and_attachment appears to be enough to enable the SAT functionality that is already present for invoices. With account_move SAT state no longer remaining None, the SAT field on the form view shows up by itself. Concern: adding 'invoice_received' state in l10n_mx_edi_document.py -> _create_update_invoice_document_from_invoice might also be needed to keep up the consistency, but I am not certain since that appears to go farther into CFDI-side logic.

task-4368532

Potential duplicate vendor bills are now kept visible even after posting, including in list views. Automatic posting is stopped when a possible duplicate is detected, helping businesses avoid accidental duplicate payments.

Purpose
=======

Recent changes have made bill encoding easier than ever (most notably, a bill date is set by default if left empty), but offering a robust duplicate bill detection is more important than ever in the modern electronic invoicing world, where bills are more and more handled automatically.

We want to make sure that:
- Potential duplicates remain visible at all time, including in list view
- Automated actions like auto posting are not done when a potential duplicate is detected.

Specs
=====

1.  Do not hide the warning on potential bill duplicate for posted invoices. The information remains pertinent.

2. When a move should be posted automatically (by the Auto-post feature on account.move or by the OCR auto-post), but a potential duplicate is found, prevent the auto-post from happening. Log the information in the chatter: "Auto-post was disabled on this invoice because a potential duplicate was detected."

3. In list view put the reference in red background when a potential duplicate on that invoice is detected.

task-4578751

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