[17.0][MIG] sale_loyalty_multi_gift: Migration to 17.0 #249
Conversation
Now we use the product field in the multi gift line as a mask for a many2many field that can be used by a third module as a way to offer optional gifts to the user. TT30850
When we've got mixed optional rewards we need to tell for sure which reward line belongs a sale line to so we can apply the right product when the reward is updated. TT34266
Currently translated at 100.0% (6 of 6 strings) Translation: sale-promotion-15.0/sale-promotion-15.0-sale_coupon_multi_gift Translate-URL: https://translation.odoo-community.org/projects/sale-promotion-15-0/sale-promotion-15-0-sale_coupon_multi_gift/es/
Currently translated at 100.0% (26 of 26 strings) Translation: sale-promotion-16.0/sale-promotion-16.0-sale_loyalty_multi_gift Translate-URL: https://translation.odoo-community.org/projects/sale-promotion-16-0/sale-promotion-16-0-sale_loyalty_multi_gift/it/
|
@HeliconiaSolutions When you depend on pending PR's, it is better to embed them here to:
That in order to help reviewers (technical and functional). |
|
/ocabot migration sale_loyalty_multi_gift |
Hi @rousseldenis , Thank you for your review! I’m reaching out regarding the process outlined in OCA Maintainer Tools. I attempted to follow the guidelines for using temporary references to another PR but am struggling to fully understand the concept and steps involved. Could you please provide a detailed explanation or some guidance on how to correctly apply this to update my PR (#249)? Any examples or best practices would be greatly appreciated, as I want to ensure I follow the correct process and adhere to the OCA standards. Thanks in advance for your help! |
Depends on