The applicant refusal wizard now displays without an unnecessary scrollbar. This makes the refusal step cleaner and easier for recruiters to use.

With this commit, the useless scroll bar in refuse reason wizard is removed.

task-4270277

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 fixes an automated mail test that could fail at a specific time each hour because it checked the message timestamp instead of the message content. The change improves test stability without affecting everyday user behavior.

In this commit, we fix this tour that failed each hour at minute 31 when the tour is runned at this time. The goal is to check the message text content and not the hour it was sent.

runbot-error-id~108435

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

Messages sent from the full composer now include both manually selected recipients and people mentioned in the message. This prevents suggested or explicitly added recipients from being dropped when mentions are used, helping ensure communications reach everyone intended.

Before this commit, when sending a message in full composer to explicit recipients and message contains mentions, the resulting recipients of the message were only mentioned users.

Steps to reproduce:
- Open a form view with suggested recipient (e.g. any contacts with demo data)
- Click "Send message" then full composer button ("expand" button)
- Type `@Marc Demo` mention in the full composer text area
- Click on "Send"

=> The new message shows envelope with only "Marc Demo" in the recipients, instead of "Marc Demo" and the suggested recipient.

This happens because when making a mention, the code to enrich the `partner_ids` of `mail.compose.message` was basically setting its content with mentions, without taking into account whether there were some explicit values with other means than with `@mention`.

This commit fixes the issue by adding mentions with the current value of `partner_ids`, so that mentions and explicit recipients are the resulting recipients of message as expected

Task-4366608

QR payment content now replaces the Vietnamese character Đ with D to avoid compatibility issues with some banks. This helps ensure payment QR codes are accepted more reliably when customer or payment details include that character.

Improvements for PR https://github.com/odoo/odoo/pull/130806


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

This update resolves a bug that prevented users from selecting the 'id' field when creating global filters within the spreadsheet edition of Odoo. Previously, this functionality was limited to relational filters. This change ensures consistent filter options for all users, improving data selection and reporting.

Steps to reproduce:
- Insert a pivot from CRM
- Create a global filter, with type date or text => The id field can be selected

With this commit, field `id` is now available only on relational global filters.

Task: 4348477

This update resolves a bug preventing the correct rendering of event templates when using sale templates in event communication settings. The fix corrects a misconfiguration in how the system searches for templates, ensuring compatibility with both event and sale templates. This improves the reliability of event communication workflows.

Current behaviour:
---
When setting mail templates in the communication tab of an event, you initially only see event templates, 
unless you click on "Search more ..." which allows you to set non-event templates.

Expected behaviour:
---
Only seeing/and being able to set event templates

Steps to reproduce:
---
1. Install event_sale
2. Go to Events, pick an event
3. In the communication tab, remove all templates
4. By clicking on "Search more ..." add a sale template
5. Set as Immediately and After each registration
6. Click on the smart button "Attendees"
7. Create a new attendee with an email then save
8. You may need to create multiple attendees
9. Failed to render inline_template template

Cause of the issue:
---
When selecting a sale template, the render model is `sale.order` So when passing the registration id to get rendered, 
it tries to read this id on a `sale.order`, causing an error if a `sale.order` with this id doesn't exist.
Caused by: https://github.com/odoo/odoo/commit/6abd149259e9caf815fe1804f1322f623f8fcb50 
`_name_search` was overriden, but the "Search more ..." option doesn't used `_name_search` but `web_search_read`

Fix:
---
Overrode `_search` instead

opw-4106237

This update resolves a bug that prevented the 'sign-up tour' from running correctly when the Odoo application was launched with only one app installed locally. The fix ensures the tour functions as expected in this common development scenario, improving the user experience for developers. This change does not impact any business functionality.

When the tour is running in single app locally, it is failing

Before this commit, the "Become Superuser" item in the debug menu was visible even if the user was not an admin. This was due to an error in the way that item was defined: it used a key "hide" that was not used by the DebugContext. Instead, it should return a falsy value, as the DebugContext uses a simple filter on the items built by their factory function. After this commit, the superuser menu is only visible to admins. Task - 4260306 --- I confirm I have signed the CLA and read

Before this commit, the "Become Superuser" item in the debug menu was visible even if the user
was not an admin.
This was due to an error in the way that item was defined:
it used a key "hide" that was not used by the DebugContext.
Instead, it should return a falsy value, as the DebugContext uses a simple filter on the items built by their factory function.

After this commit, the superuser menu is only visible to admins.

Task - 4260306

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

Forward-Port-Of: odoo/odoo#186584