Skip to content

[19.0][MIG] mail_activity_team: Migration to 19.0#153

Open
muaazsiddiq wants to merge 80 commits intoOCA:19.0from
initOS:19.0-mig-mail_activity_team
Open

[19.0][MIG] mail_activity_team: Migration to 19.0#153
muaazsiddiq wants to merge 80 commits intoOCA:19.0from
initOS:19.0-mig-mail_activity_team

Conversation

@muaazsiddiq
Copy link

No description provided.

JordiBForgeFlow and others added 30 commits February 13, 2026 12:22
Currently translated at 100.0% (24 of 24 strings)

Translation: social-13.0/social-13.0-mail_activity_team
Translate-URL: https://translation.odoo-community.org/projects/social-13-0/social-13-0-mail_activity_team/it/
When an activity is scheduled due to automatic processes the onchanges
won't adapt the proper user team, so we could have a mismatch that
provokes an exceptions due to the designed constaints
- If a user is archived but there's an automatic activity, the team
check wouldn't locate him. We have to ensure the context.
- When the automatic activity gets a user with no team, we should set
the team to a void one as well.

TT30470
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: social-15.0/social-15.0-mail_activity_team
Translate-URL: https://translation.odoo-community.org/projects/social-15-0/social-15-0-mail_activity_team/
If you schedule an activity and you don't force the team as False, errors might araise.
For example, on holidays.
The user couldn't see the proper count of his own activities. It was
allways showing the team activities counter.

TT35885
weblate and others added 21 commits February 13, 2026 12:22
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: social-17.0/social-17.0-mail_activity_team
Translate-URL: https://translation.odoo-community.org/projects/social-17-0/social-17-0-mail_activity_team/
Currently translated at 100.0% (34 of 34 strings)

Translation: social-17.0/social-17.0-mail_activity_team
Translate-URL: https://translation.odoo-community.org/projects/social-17-0/social-17-0-mail_activity_team/it/
A monkey patch is required on mail.activity's create method to prevent an
unboundError (see odoo/odoo#197864).

In order to open the team activities (Late/Today/Future) from the systray widget,
domain clause mangling is applied in mail.activity.mixin's web_search_read.

Includes OCA/social#1469 that was not ported to 17.0 yet.

Aligned ir.rule with upstream mail.activity rule wrt. creation
(https://github.com/odoo/odoo/blob/b1ffd68e4094d9456dd4ae8f0fa12b50e5ce9d67/addons/mail/security/mail_security.xml#L223-L232).

Co-authored-by: Wodran Van de Sande <wodran.vandesande@dynapps.be>
…s provided

mail.activity's `create` checks if a value for `team_id` is being passed, and
in that case drops values for `user_id`. However, a value for `team_id` will
always be present in the create values because there is a default method for
the field.

In case all teams have been deleted, or if team selection is restricted as per
customization, the value for `team_id` will still be present, but empty. In
that case, we don't want the value for `user_id` to be dropped silently from
the values.
mail_post_defer breaks tests for mail_tracking, so it's better to split it.
OCA/social@b782115
@moduon MT-10471
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: mail-18.0/mail-18.0-mail_activity_team
Translate-URL: https://translation.odoo-community.org/projects/mail-18-0/mail-18-0-mail_activity_team/
Currently translated at 100.0% (35 of 35 strings)

Translation: mail-18.0/mail-18.0-mail_activity_team
Translate-URL: https://translation.odoo-community.org/projects/mail-18-0/mail-18-0-mail_activity_team/it/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: mail-18.0/mail-18.0-mail_activity_team
Translate-URL: https://translation.odoo-community.org/projects/mail-18-0/mail-18-0-mail_activity_team/
Currently translated at 100.0% (35 of 35 strings)

Translation: mail-18.0/mail-18.0-mail_activity_team
Translate-URL: https://translation.odoo-community.org/projects/mail-18-0/mail-18-0-mail_activity_team/it/
@muaazsiddiq muaazsiddiq mentioned this pull request Feb 23, 2026
33 tasks
Copy link
Member

@mathiasfrancke mathiasfrancke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One optional change. Tests pending

# We must consider also users that could be archived but come from
# an automatic scheduled activity
if (
activity.user_id.id != api.SUPERUSER_ID
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(optional) we could import SUPERUSER_ID from api so we can use SUPERUSER_ID here instead of api.SUPERUSER_ID

@mathiasfrancke
Copy link
Member

mathiasfrancke commented Feb 23, 2026

@muaazsiddiq Some checks are failing

Copy link
Member

@mathiasfrancke mathiasfrancke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested successfully

Copy link
Contributor

@CRogos CRogos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are several PR on v18. https://github.com/OCA/mail/pulls?q=is%3Apr+is%3Aopen+mail_activity_team
I think at least the outcome of #116 and #149 should be added before the migration.

Also the changes need to be squashed into one commit and there are also a lot of commits which could be squashed: https://github.com/OCA/maintainer-tools/wiki/Merge-commits-in-pull-requests#mergesquash-the-commits-generated-by-bots-or-weblate

@muaazsiddiq muaazsiddiq force-pushed the 19.0-mig-mail_activity_team branch from 9d12d79 to 5fe7b94 Compare February 27, 2026 13:56
@muaazsiddiq
Copy link
Author

@CRogos

  • I have squashed the commit.
  • I will add above mentioned PRs once they get merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.