Skip to content

[17.0][MIG] loyalty_criteria_multi_product: Migration to 17.0 #240

Open
BhaveshHeliconia wants to merge 12 commits into
OCA:17.0from
HeliconiaIO:17.0-mig-loyalty_criteria_multi_product
Open

[17.0][MIG] loyalty_criteria_multi_product: Migration to 17.0 #240
BhaveshHeliconia wants to merge 12 commits into
OCA:17.0from
HeliconiaIO:17.0-mig-loyalty_criteria_multi_product

Conversation

@BhaveshHeliconia

Copy link
Copy Markdown
Contributor

No description provided.

@BhaveshHeliconia
BhaveshHeliconia force-pushed the 17.0-mig-loyalty_criteria_multi_product branch from aad513a to 1521d52 Compare February 6, 2025 10:25
@BhaveshHeliconia
BhaveshHeliconia force-pushed the 17.0-mig-loyalty_criteria_multi_product branch from 1521d52 to 811066a Compare March 31, 2025 10:44
@BhaveshHeliconia
BhaveshHeliconia force-pushed the 17.0-mig-loyalty_criteria_multi_product branch from 811066a to ed46a1d Compare July 25, 2025 10:23
@BhaveshHeliconia
BhaveshHeliconia force-pushed the 17.0-mig-loyalty_criteria_multi_product branch from ed46a1d to fdbdfb8 Compare October 27, 2025 04:48
@BhaveshHeliconia

Copy link
Copy Markdown
Contributor Author

Hey @OCA/crm-sales-marketing-maintainers would be great if someone could have a look at this module.

@github-actions

github-actions Bot commented Mar 1, 2026

Copy link
Copy Markdown

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions Bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Mar 1, 2026
@BhaveshHeliconia
BhaveshHeliconia force-pushed the 17.0-mig-loyalty_criteria_multi_product branch from fdbdfb8 to 4d65605 Compare March 5, 2026 04:51
@github-actions github-actions Bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Mar 8, 2026
@BhaveshHeliconia
BhaveshHeliconia force-pushed the 17.0-mig-loyalty_criteria_multi_product branch from 4d65605 to 0fe8841 Compare March 9, 2026 04:14
@BhaveshHeliconia

Copy link
Copy Markdown
Contributor Author

Hey @OCA/crm-sales-marketing-maintainers would be great if someone could have a look at this module.

@github-actions

Copy link
Copy Markdown

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions Bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jul 12, 2026
stefan-tecnativa and others added 12 commits July 13, 2026 10:21
…16.0

- Migration scripts
- Adapt views and tests
- Set correct permissions
- Move loyalty.criteria(coupon.criteria) model from loyalty.program to loyalty.rule

TT44317
Currently translated at 100.0% (21 of 21 strings)

Translation: sale-promotion-16.0/sale-promotion-16.0-loyalty_criteria_multi_product
Translate-URL: https://translation.odoo-community.org/projects/sale-promotion-16-0/sale-promotion-16-0-loyalty_criteria_multi_product/it/
They should bne hosted in a version numbered folder.
…iteria + repeat_product

- It should be VARCHAR, not CHAR.
- Remove the condition for assigning the rule (as there can be m2m
  linked products although there criteria selection is another).
- Do the product m2m handle.
- Do the repeat_product handlement by SQL + fix it.
The loyalty_criteria field data, previously in the loyalty_program
table (coupon_program) must be moved completely, both the value
'multi_product' and 'domain' to the loyalty_rule table where this
data must now be stored. Otherwise the data 'domain' will be lost.

TT44317
…oduct promotion criteria

When setting up a multi-product promotion, you should not set a minimum
spend amount because if one rule passes, they will all pass.
To avoid misconfiguration, the field is hidden for promotions
with multi-product criteria. In addition, the rule data is cleared
when the criterion is changed so that the promotion is applied
correctly in case of promotion modifications.
@BhaveshHeliconia
BhaveshHeliconia force-pushed the 17.0-mig-loyalty_criteria_multi_product branch from 0fe8841 to 1fb7e65 Compare July 13, 2026 04:51
@OCA-git-bot OCA-git-bot added series:17.0 mod:loyalty_criteria_multi_product Module loyalty_criteria_multi_product labels Jul 13, 2026
@github-actions github-actions Bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jul 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mod:loyalty_criteria_multi_product Module loyalty_criteria_multi_product series:17.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants