This update ensures that refused time off requests are now correctly displayed as 'struck out' in the calendar view within the Overview menu. Previously, these requests weren't visually marked, leading to confusion. This change improves clarity and accuracy for HR staff managing time off requests.

Before this commit, the calendar view in Overview menu does not strike the time off refused. The reason is because `is_strike` field is not fetched inside that view.

This commit adds the field in the view to make sure the time off refused are striked as it is the case in the other menus.

Closes #248868

This update fixes a potential issue in the payment demo module by ensuring that provider configurations are properly validated. This enhances the stability and reliability of the demo, preventing unexpected errors related to payment provider setup. It's a routine maintenance update to improve the demo's functionality.

opw-3097856

This update corrects a technical detail by removing outdated XML tags (<report> and <act_window>) from the Odoo import file. These tags were previously removed in another change, but the import file hadn't been updated. This ensures consistency and prevents potential issues during Odoo installation or updates.

`<report>` and `<act_window>` tags has been removed in https://github.com/odoo/odoo/pull/98138, but not in the import_xml.rng file.
This commit removes the two tags from the file.

This update resolves an issue where deleting and recreating the Contact Us form on the website caused submission errors. The fix ensures the form correctly uses the current form data, preventing this mismatch and restoring proper functionality. This improves the user experience for website visitors.

Problem: There is a data-for span in the /contactus page that sets specific values on the page's form. If this form is deleted and a new form is added, an error will occur when trying to submit the new form. This is because the value set for website_form_signature will use the email set in the data-for, which will not match with the new form.

Purpose: Modify the code that sets the website_form_signature value to ensure that the original form is present as well if using the data-for values.

Steps to Reproduce in Runbot:

1. Use the Website Editor to delete the form on the /contactus page and create a new one.

2. Attempt to submit the new form.

opw-5956030

This update corrects a recent change in the URL required to send e-invoices to the Serbian government. This ensures that invoices are correctly submitted, avoiding potential delays or errors in processing. The change was necessary due to an update from the Serbian tax authority.

**PROBLEM**
The url to send e-invoice to the serbian government has changed.

opw-6055622

This update fixes a translation error that was displaying the incorrect 'Tax ID' label ('CPF/CNPJ') for Odoo users in Mozambique. The change ensures that the correct 'NUIT' label is shown, aligning with Mozambique's tax ID system. This was reported by functional support and improves data accuracy for our Mozambique customers.

Currently the "Tax ID" title used e.g. on sales orders, invoices, etc. was translated as "CPF/CNPJ" in Portuguese, which is the tax ID used in Brazil. However, in Mozambique, the tax ID is called "NUIT", and there is no language variant for Portuguese in Mozambique. This caused Mozambique users to see "CPF/CNPJ" instead of "NUIT" on their documents, which was wrong.

This commit adds a `vat_label` field for Mozambique to display the correct tax ID label.

Issue reported by functional support.

This update enhances the testing process for Odoo apps submitted to the Odoo Apps Store. Specifically, it adds support for price and currency information within the manifest file, ensuring accurate validation and pricing data is captured. This improves the quality and reliability of apps available on the Odoo Apps Store.

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

This update resolves an issue where users would receive an access rights error when creating private tasks without a project or assigned users. The fix ensures that the task creator automatically gains access rights upon creation, preventing this error and improving task creation flow. This change impacts the task management process.

When users would follow the following step as they are makeing a private task,  they would be hit by an incorrect access error.

Steps to reproduce:
1.Open the form view to create a new task.
2.Clear the Project field. When empty, it should display the Private placeholder. 3.Ensure no user is assigned to the task.
4.Create the private task.
5.An access rights error occurs, stating that the user does not have permission to create the record.

⚠️ Note:
This access rights error only occurs when the task is created directly as private. If a task is created normally and then its project_id and user_ids are removed afterward, no access rights error occurs.

Root cause:
When a task is created without a project_id and without assigned users, Odoo checks access rights on creation. Since no project members or assigned users exist, no user has access to the record, including the creator. This results in an access rights error during creation.

This issue does not occur when modifying an existing task because, after creation, the creator is automatically added as a follower. As a follower, the creator retains access to the task even if it has no project and no assigned users.

Fix (implemented):
Tasks that have no assigned users and are not linked to any project (private tasks) did not make sense, as they were effectively assigned to nothing.
To address this, we now require at least one user to be assigned to a task when it is not attached to a project.  This change was made inside of the "project_task_view.xml" file in the "view_task_form_2" record


Versions : 17.0 -> master
Task [5403926](https://www.odoo.com/odoo/project/4105/tasks/5403926)
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr