Skip to content

[17.0][FIX] mass_mailing_partner: Add partner_unique option to lists#1835

Merged
OCA-git-bot merged 1 commit into
OCA:17.0from
Tecnativa:17.0-fix-mass_mailing_partner-TT61525-v2
May 8, 2026
Merged

[17.0][FIX] mass_mailing_partner: Add partner_unique option to lists#1835
OCA-git-bot merged 1 commit into
OCA:17.0from
Tecnativa:17.0-fix-mass_mailing_partner-TT61525-v2

Conversation

@victoralmau
Copy link
Copy Markdown
Member

@victoralmau victoralmau commented Mar 25, 2026

Add partner_unique option to lists

The partner_unique field is added to the lists; the existing validation error (multiple contacts with the same partner) will only be displayed if this field is checked.

Related to b769848

Please @pedrobaeza and @pilarvargas-tecnativa can you review it?

@Tecnativa TT61525

@pedrobaeza pedrobaeza added this to the 17.0 milestone Mar 25, 2026
Copy link
Copy Markdown
Member

@pedrobaeza pedrobaeza left a comment

Choose a reason for hiding this comment

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

Yes, if Odoo allows to have the same mail several times in the same list, we should allow to have the same partner in the same list. I'm now thinking that maybe we should provide this as a configuration option at list level.

The partner_unique field is added to the lists; the existing validation error (multiple contacts with the same partner) will only be displayed if this field is checked.

Related to OCA@b769848

TT61525
@victoralmau victoralmau force-pushed the 17.0-fix-mass_mailing_partner-TT61525-v2 branch from 02478e3 to 85e1584 Compare March 25, 2026 16:04
@victoralmau victoralmau changed the title [17.0][FIX] mass_mailing_partner: Allow multiple contacts (list) with the same partner [17.0][FIX] mass_mailing_partner: Add partner_unique option to lists Mar 25, 2026
@victoralmau victoralmau requested a review from pedrobaeza March 25, 2026 16:22
@OCA-git-bot
Copy link
Copy Markdown
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@pedrobaeza
Copy link
Copy Markdown
Member

/ocabot merge minor

@OCA-git-bot
Copy link
Copy Markdown
Contributor

On my way to merge this fine PR!
Prepared branch 17.0-ocabot-merge-pr-1835-by-pedrobaeza-bump-minor, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 3e93c4c into OCA:17.0 May 8, 2026
9 checks passed
@OCA-git-bot
Copy link
Copy Markdown
Contributor

Congratulations, your PR was merged at dae55e5. Thanks a lot for contributing to OCA. ❤️

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants