When an unbuild order linked to a manufacturing order is completed, the system now automatically logs a note on the manufacturing order. This improves traceability by making it easier for users to see when and why a produced item was unbuilt.

This commit makes it so a note is logged when an unbuild order is linked
to a manufacturing order is completed.

Task: 2378831

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

This change simplifies Odoo's internal testing framework so two similar test approaches now behave consistently. It helps developers write faster, more reliable tests and reduces the chance that one test affects another, without changing day-to-day user features.

Essentially make both classes be the same one, and behave like `SavepointCase`.

Website editors can now customize all five default palette colors used in illustrations, instead of only the first one. This gives businesses more control over matching illustrations to their brand colors and improves visual consistency across pages.

Before this commit only the first default palette color was configurable
on illustrations

After this commit all 5 default palette colors are configurable on
illustrations

task-2368585

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

Generated documents will no longer include unwanted blank lines caused by template indentation. This improves document presentation by removing extra whitespace at the start and within generated content.

The way QWeb handles text nodes and node tails makes it generate
white spaces copied from the XML indentation even before the first
useful character

Before this commit blank lines appeared at the beginning of generated
documents as well as inside the document content

After this commit no blank lines appear at the beginning of generated
documents and blank lines inside document are removed

task-2366756

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

Marketing users can now plan and review email and SMS campaigns in a calendar view, making it easier to coordinate upcoming communications. Scheduling is also handled directly on the campaign form, with safeguards to prevent selecting dates in the past.

PURPOSE

To ease the scheduling process, we introduce a new calendar view on mailings
that allows to easily schedule your communications.
In addition, mailings/sms views were pimped to improve the global usability,
especially on the scheduling configuration.

SPECS

- add a calendar view to allow marketeers to either schedule or overview their
  ongoing mailings/sms ;
  Side note: inspired by what has been done with Social Posts
- improve the scheduling flow by allowing to configure it directly in the form
  view using fields rather than action buttons that open an extra window ;
- add a constraint on 'schedule_date' to make sure it's not scheduled in the
  past ;
- update mass_mailing_sms to match scheduling flow of emails and adjust the
  'sms_force_send' display to ease understanding ;

LINKS

Task ID 2202759

Co-authored-by: Aurélien Warnon <awa@odoo.com>

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 change updates many automated tests to use a newer shared testing approach and fixes an issue in Belgian payroll test setup. It helps make future development safer by reducing fragile test behavior, with no expected change for day-to-day users.

Marketing Automation was updated to stay aligned with recent changes in the related mailing system. This helps ensure existing marketing automation views continue to work correctly after the underlying naming updates.

This commit is simply the follow-up of the community counterpart where we had
to rename a few XML elements.

Task ID 2202759
Community PR odoo/odoo#57000

Employee work locations are now managed as reusable records instead of free-text entries, making location information more consistent across HR processes. Related appraisal, payroll, demo, and timesheet data were adjusted so these areas continue to use the updated location structure.

The work location of an employee was previously a fields.Char. That was changed to a Many2one field to a the new model called work.location.
That had some consequences in other modules that had to be slightly adjusted.
The modules impacted were hr, hr_appraisal, hr_payroll.

TaskID: 2335646