A new demo module lets teams showcase and explore the Social app without connecting to external social media APIs. This provides a safe environment for trying posts, comments, and streams, making customer demonstrations and training easier.

This commit introduces a new complete demo module for the social app.

A full module is necessary because we need to override several methods to prevent calls to third
party APIs.

This creates a full sandbox where you can safely play around with posts and comments while checking
the capabilities of our social app.
It will also make it easier to showcase the app to new customers.

Task#2081610

Certification badges are now shown separately from other eLearning badges on the ranks page, making achievements tied to courses easier to find and understand. Users can click a certification badge to go directly to the related course, while background updates improve badge and challenge organization.

This merge adds a section to distinguish the certification badges from the
other badges users may obtain in eLearning. Certification badges are available
on the ranks page, linked to a running survey. Clicking on them directly
redirects into the linked course.

Other commits in this merge include

  * renaming a category field on challenge to challenge_category to ease
    its finding in code;
  * renaming some statistics fields on badge model to ease its understanding;
  * various usability improvements and fixes;

Task ID : 1961053
PR #32594

Odoo now includes user records when automatically applying company-based restrictions. This helps keep stock and product-related selections aligned with the correct company, reducing mistakes in multi-company setups.

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

This change prevents duplicate company-specific default values from being saved for the same setting, which could previously cause inconsistent results. It improves reliability across accounting, inventory valuation, point of sale, product, website learning, and core system flows by ensuring the system uses one clear value.

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

Time off types can now use different approval rules for allocation requests and actual leave requests. This gives businesses more control, such as allowing a manager to approve earned compensation days while another role handles later time off requests.

Purpose
=======

We want to allow different approvals for allocations and leaves of a same type.

e.g. In case of compensation days, a manager would approve the
allocation request, but would later not approve leave requests.

Specification
=============

Allocation modes
----------------
No change here except renames.
1. No limit (employee doesn't need an allocation to request a leave)
2. Allow employee requests
3. Fixed by Time Off Officer

Allocation approval
-------------------
A radio field to choose the approval mechanism
appears if the employee is allowed to request an allocation.
The following approval modes are possible:
1. Time Off Officer
2. Employee's Time Off Manager (leave_responsible_id)
3. Employee's Time Off Manager and Time Off Officer

These options are the same as leave approval options
(except the missing "No Validation").

If option 1 or 2 is selected, a o2m field should
allow to select which Time Off Officer is responsible
for approving those allocations.

Additional changes
------------------

The field `code` of a leave type is unused and thus
removed. A code is usefull for payroll purposes
and is added by hr_payroll module.

A stat button on a leave type counting how many allocation
have bee made does not have any sens if no allocation is
required. Therefore we remove it in this case.

Task id: 1936742

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

Inventory adjustments are easier to find and start from the inventory app. Users can open draft or in-progress adjustments directly in the barcode view and create a new adjustment from scratch, improving day-to-day warehouse efficiency.

shows a kanban view of the draft and in progress inventory adjustment, I click on it, it opens the barcode view of the inventory adjustment and  add a create button to start an inventory adjustment from scratch to provide more efficiency and convenience to user.

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

Pad : https://pad.odoo.com/p/r.14bd692e7a6b5301c19b90bc044729b3





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

Project tasks can now be organized into multiple nested sub-task levels instead of only one. This gives teams more flexibility to break down complex work, while keeping sub-task counts, naming, project assignment, and planned or effective hours aligned across the hierarchy.

Purpose
=======

Currently, it is only possible to have 1 level of sub-tasks per task.
The user may want several levels of granurality.

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

Allow having multi levels of sub-tasks
- Move the parent_id field out of the debug mode and display it above the
  Deadline field
- Remove the 'parent task' stat button
- Add the parent_id field to the project.task optional list view
- Display the sub-tasks stat button on sub-tasks
- The 'sub-tasks' stat button should only count/display tasks from the
  first level of sub-tasks
- The name of the sub-task should be
  parent task: sub task level 1: sub task level 2: sub task level 3...
- The sub-task should be created in the sub-task project set on the
  parent task's project
- The subtask_planned_hours and the subtask_effective_hours fields should
  take into account the planned hours of all sub-level tasks

TaskID: 2107078

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

HR users can now update selected employee, contract, recruitment, expense, leave, and work entry fields in bulk from list views. This reduces repetitive manual updates and makes maintaining HR data faster and more consistent.

Make some fields editable in multi edit.
Some onchange are transformed in compute fields.

id=2078674





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

Field Service can now be used without requiring the Sales app, making it easier for teams that only need planning and operations workflows. Sales-related billing features are moved into separate add-on modules that activate when sales functionality is installed.

Inventory adjustments now open in a kanban view that highlights draft and in-progress adjustments, making it easier for users to continue existing work or start a new adjustment. Barcode inventory adjustments also better support multi-location and multi-warehouse setups by avoiding an incorrect location warning.

shows a kanban view of the draft and in progress inventory adjustment, I click on it, it opens the barcode view of the inventory adjustment and  add a create button to start an inventory adjustment from scratch to provide more efficiency and convenience to user.

Task : https://www.odoo.com/web#id=1970451&action=327&model=project.task&view_type=form&menu_id=4720
Pad : https://pad.odoo.com/p/r.14bd692e7a6b5301c19b90bc044729b3

HR teams can now update selected contract and employee-related fields across multiple records at once. This reduces repetitive data entry and keeps related values updated automatically when changes are made.

Make some fields editable in multi edit.
Some onchange are transformed in compute fields.

id=2078674