Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport] Fixed issue if there are multiple skus in catalog rule condition combination #21269

Merged

Conversation

mage2pratik
Copy link
Contributor

Original Pull Request

#20923

Fixed issue if there are multiple skus in catalog rule condition combination

Description (*)

In catalog rule, if there are multiple skus and the condition is 'in one of' then the discount applies only on the first sku.

Fixed Issues (if relevant)

Manual testing scenarios (*)

  1. Have a Magento v2.3 clean installation.
  2. Go to Stores > Attributes > Product and edit sku attribute.
  3. Go to Storefront Properties tab and set YES for Use for Promo Rule Conditions.
  4. Go to Marketing > Promotions > Catalog Price Rule and Add New Rule.
  5. Create a new rule, select SKU as the product attribute from the condition dropdown, select is one of as a condition and select more than one SKU in the value.
  6. Click on Save and Apply.
  7. Refresh Magento cache by navigating System > Tools > Cache Management.
  8. Before: On the frontend, the discount applies only on the first SKU from the condition.
    After: The discount applies on all the products from the condition.

Following are the before after videos of the issue:

Before Video

After Video

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

@magento-engcom-team
Copy link
Contributor

Hi @mage2pratik. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento-engcom-team give me test instance - deploy test instance based on PR changes
  • @magento-engcom-team give me 2.2-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

@magento-engcom-team
Copy link
Contributor

Hi @VladimirZaets, thank you for the review.
ENGCOM-4291 has been created to process this Pull Request

@sivaschenko
Copy link
Member

@magento-engcom-team give me test instance

@magento-engcom-team
Copy link
Contributor

Hi @sivaschenko. Thank you for your request. I'm working on Magento instance for you

@magento-engcom-team
Copy link
Contributor

Hi @sivaschenko, here is your new Magento instance.
Admin access: https://pr-21269.instances.magento-community.engineering/admin
Login: admin Password: 123123q

@sivaschenko sivaschenko self-assigned this Feb 17, 2019
@magento-engcom-team magento-engcom-team merged commit 1750a58 into magento:2.2-develop Feb 18, 2019
@ghost
Copy link

ghost commented Feb 18, 2019

Hi @mage2pratik, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

magento-engcom-team pushed a commit that referenced this pull request Feb 18, 2019
@magento-engcom-team magento-engcom-team added this to the Release: 2.2.9 milestone Feb 18, 2019
@mage2pratik mage2pratik deleted the 2.2-develop-PR-port-20923 branch March 26, 2021 08:35
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.

6 participants