Users can now assign taxes directly on accounting lines when creating a new journal entry, with tax lines computed immediately as the entry is edited. This makes manual entry creation smoother and helps ensure tax amounts are visible and accurate before saving.

Allow the user to set taxes on lines when creating a new account.move.

task: https://www.odoo.com/web#id=33802&view_type=form&model=project.task&action=333&active_id=967&menu_id=4720
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Odoo email templates across events, projects, gamification, ratings, and product emails were refreshed with cleaner layouts and better formatting for email readers. The change also makes notification emails easier to customize, helping businesses send more polished and consistent customer communications.

Description of the issue/feature this PR addresses:
task link -
https://www.odoo.com/web#id=51122&view_type=form&model=project.task&action=327&menu_id=
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

Fleet users can now search vehicles by the driver they were assigned to using the “Assigned to” filter. This makes it easier to review which vehicles have been linked to a specific driver over time, improving fleet tracking and reporting.

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

Odoo can now apply conditional color styling to all field widgets, not just limited views. This helps users quickly spot important record states, such as whether a VAT number is validated, using familiar visual indicators like success or danger colors.

It is sometimes useful to be able to customize slightly the color of a
field depending on some conditions on the current record.

For example, imagine that we want to show a VAT number field in green/red, if
it was validated or not. To do that, we can add a field with an
onchange, and simply add decoration-danger and decoration-success
attributes to the field.

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

The recruitment app now lets users mark each candidate pipeline item with a visual status, similar to project tasks. This makes it easier for hiring teams to quickly see and filter applications by their current attention or readiness state.

project : RD for Dummies

task : [hr_recruitment] Y U NO HAZ KANBAN STATE

This update refreshes several customer-facing email templates so messages look cleaner, more consistent, and more aligned with Odoo's standard notification style. It improves communications for helpdesk tickets, sales coupons, and online signature requests, giving recipients a more polished experience.

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

Odoo Studio now better preserves field settings when users move fields around in customized views. This reduces the risk of later app updates or module installations overwriting or losing attributes in Studio-created layouts.

Before this rev. the view normalization was only creating `replace` or `add`
xpaths while parsing the diff between the archs with and without the Studio view.

This approach was not optimal for moved fields, mainly because all attributes
were copied on the `add` xpath. If the Studio view was created before installing
a new module that modified a attribute for example, this one would have been
lost in the process.

With `move` xpath, the entire node (and its attributes) are moved.

The normalization thus needed to be able to spot these moved fields and create
the corresponding xpaths. To do so, we spot fields appearing in both '-' and '+'
lines in the diff.

This heuristic however is not complete. Imagine the following situation where a
field in a group is moved in the upper group. The diff, instead of writing '-'
and '+' for the field, will move the boundary of the group.

Like
...
  /data/form/sheet/group/group/field[@name=website]
  /data/form/sheet/group/group/field[@name=website][@closed]
- /data/form/sheet/group/group[@closed]
- /data/form/sheet/group/group
  /data/form/sheet/group/group/field[@name=function]
  /data/form/sheet/group/group/field[@name=function][@closed]
+ /data/form/sheet/group/group[@closed]
+ /data/form/sheet/group/group
...

The normalization thus needs to spot these cases where the group boundaries are
moved and declare all the fields inside as moved fields.

Moving boundary algorithm is a joint work with @dmo-odoo.

cc @mge-odoo @Elkasitu