Odoo Changelog — 2026-07-08

Wednesday, July 8, 2026

2 changes · saas-18.2

Bug Fixes(2)

Resolved issues and error corrections

[FIX] appointment: prevent error on update resource capacity

PR #122095

Enterprisesaas-18.2appointment

Canceled appointment bookings will no longer prevent staff from reducing a resource's capacity. This avoids an error after cancellations and keeps resource capacity management aligned with active bookings only.

Original PR description

Steps to reproduce:
1. Install `appointment`
2. Create an appointment type using resources
3. Create a resource with capacity `4`
4. Book an appointment on that resource with reserved capacity `4`
5. Try to reduce the resource capacity
6. Cancel the appointment
7. Try again to reduce the resource capacity

Current behavior:
- Reducing the resource capacity raises: `The capacity used can not be lesser than the capacity reserved`

Issue:
- Canceled appointments still prevent lowering the resource capacity, even though the booking is no longer active.

Cause:
- Canceling an appointment only archives the related `calendar.event`, it does not remove the corresponding `appointment.booking.line`. That booking line keeps its previous `capacity_reserved` value, while `capacity_used` is a stored computed field depending on the resource capacity. When the resource capacity is reduced after cancellation, the archived booking line is recomputed with the new lower resource capacity and this violates the SQL constraint

Solution:
- For inactive booking lines: Set `capacity_used = capacity_reserved`

opw-6036053

Forward-Port-Of: odoo/enterprise#112485

#appointments#resources#capacity#cancellations

[FIX] social_twitter: store tweet reply count

PR #122846

Enterprisesaas-18.2social_twitter

Twitter/X social stream posts now save the reply count provided by the platform's API. This ensures comments are shown alongside other engagement metrics, giving users a more complete view of tweet performance.

Original PR description

Twitter/X tweet metrics returned by the API include the number of replies in the `public_metrics.reply_count` field.

This commit stores that value on social stream posts so the comments count can be displayed alongside other engagement metrics.

API Documentation: https://docs.x.com/x-api/fundamentals/metrics#post-metrics

Task-6251172

Forward-Port-Of: odoo/enterprise#120182

#twitter#social#metrics#engagement

Steps to reproduce: 1. Install `appointment` 2. Create an appointment type using resources 3. Create a resource with capacity `4` 4. Book an appointment on that resource with reserved capacity `4` 5. Try to reduce the resource capacity 6. Cancel the appointment 7. Try again to reduce the resource capacity Current behavior: - Reducing the resource capacity raises: `The capacity used can not be lesser than the capacity reserved` Issue: - Canceled appointments still prevent lowering the resource capacity, even though the booking is no longer active. Cause: - Canceling an appointment only archives the related `calendar.event`, it does not remove the corresponding `appointment.booking.line`. That booking line keeps its previous `capacity_reserved` value, while `capacity_used` is a stored computed field depending on the resource capacity. When the resource capacity is reduced after cancellation, the archived booking line is recomputed with the new lower resource capacity and this violates the SQL constraint Solution: - For inactive booking lines: Set `capacity_used = capacity_reserved` opw-6036053 Forward-Port-Of: odoo/enterprise#112485

Twitter/X tweet metrics returned by the API include the number of replies in the `public_metrics.reply_count` field. This commit stores that value on social stream posts so the comments count can be displayed alongside other engagement metrics. API Documentation: https://docs.x.com/x-api/fundamentals/metrics#post-metrics Task-6251172 Forward-Port-Of: odoo/enterprise#120182