In the Time Off app dashboard, employees can view whether some of their unused time off days are set to expire and the exact expiration date.

At the accrual plan level, a validity period can be defined for carried-over days, after which they expire. However, the expiration date of these carried-over days hasn't been considered when calculating the employee's expiring balance.

Steps to reproduce:  
1. Create a new accrual plan.  
2. Define a new accrual plan level.  
3. Configure the level to accrue 10 days annually.  
4. Set the carryover validity to 2 months.  
5. Keep all other settings as default.  
6. Create a new allocation.  
7. Apply the previously defined accrual plan.  
8. Set the start date to 01/01/20xx (where xx is the previous year).  
9. Confirm the employee's balance is now 10 days.  
10. Navigate to the dashboard.  
11. Set the date to 01/01/(20xx + 2), corresponding to the carryover date.  
12. Notice that no expiration date is displayed on the dashboard.  
13. The expiration date should be displayed as 01/03/(20xx + 2).

This update addresses the issue by incorporating the expiration dates of carried-over days into the calculation.

task-4207987

How to reproduce:
–	Revert fix: odoo/odoo#206361 which fix archived activities not being deleted when their related record are
–	Install project and log as admin
–	In Settings -> Activity Type -> To-Do -> check “Keep Done” –	In Project -> Office Design -> Energy Certificate -> Schedule an activity To-Do for “Marc Demo” (it must be another user)
–	Mark it as done
–	Delete the task (cog menu)
–	Click on the clock on the top right
–	And then on “View all activities”
–	Remove all filters
–	Add filter “Done”
You get a “Missing Record” error: “Record does not exist or has been deleted.”

The error happens on
allowed_ids[res_model] = set(records._filtered_access(operation)._ids) because records contains the deleted task.
Note that this line is bypassed for activities of the current user, that’s why it is important to assign the test activity to another user.

We solve the problem by restraining the records to the existing one (using .exists on the recordset). Note that in v17, there is no problem because _filter_access_rules (with check_access_right) was used instead of _filtered_access.

We've considered to clean the records as they were detected in the mail_activity _search method but that was not straightforward as it is usually executed with a readonly transaction (web_search_read) and there is any way already an upgrade script which suppress all orphan activities: https://github.com/odoo/upgrade/pull/6952.

Technical note: the test doesn't reproduce exactly the problem (no exception) but we check that the records are filtered as explained above.

Task-4730338

Description of the issue this commit addresses:

In the move form view, the sections and notes are made readonly too soon. For example in a purchase order form, when the PO is confirmed, it is still possible to add notes and sections but not to edit them so they are locked once the focus is lost. As it is intended to be able to add notes at such point so it should be possible to edit them too.

---

Desired behavior after this commit is merged:

This commit makes it so that the readonly attribute of the sections and notes depends on the state of the move of the form. Currently, we want the readonly only if the parent is cancelled (cancel), locked (done) or posted (posted).

---

Note on the fix:

The addition of the sectionAndNoteIsReadonly() getter is the part of the fix
that really allows the user to edit text that was previously uneditable. On the
other hand, the override of the isCellReadonly method is only here to make sure
no readonly classes like text-muted are applied if the cell is still editable.

---

opw-4744367

---

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

Before this commit, when an user A is invited by an event of user B and none of these users are synchronized with Outlook, when the synchronization of user A starts or resumes, the event will be synchronized without any organizer in user A's Outlook calendar due to a limitation of Microsoft of not accepting creating events for other users (user B) directly. In the meanwhile, in Odoo, the event ownership will be transferred from user B to user A, which is also wrong.

After this commit, when user A starts or resumes its synchronization with Outlook, previous Odoo events which user A is attendee but not organizer won't be synchronized until the organizer synchronizes its calendar. This will keep the ownership of the event intact in Odoo, and when the organizer synchronizes its calendar with Outlook, it will be correctly synchronized in Outlook as well. This approach will also reduce the possibility of duplicated events in Odoo side (and by transitivity, in Outlook side).

task-4269432