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] Fix configurable dropdown showing tax incorrectly in 2.3-develop #22535

Conversation

amol2jcommerce
Copy link
Contributor

Original Pull Request

#22466

Description (*)

This pull request addresses an issue described in #22270 and introduced in #17695.

The issue is that the price increase calculation was previously based upon the configurable basePrice vs the optionFinalPrice rather than the configurable finalPrice vs the optionFinalPrice. This meant that the tax amount was also been added to the price difference calculation for each of the configurable options incorrectly.

Fixed Issues (if relevant)

  1. 2.2.8 Configurable product option dropdown - price difference incorrect when catalog prices are entered excluding tax #22270: 2.2.8 Configurable product option dropdown - price difference incorrect when catalog prices are entered excluding tax

Manual testing scenarios (*)all Magento 2.

  1. Set prices to be entered excluding tax in the configuration.
  2. Apply product tax using tax rules.
  3. Create a configurable product configurable by only one dropdown attribute (e.g colour or size)
  4. Ensure that the product tax is not added for a second time in the dropdown attribute

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)

… decreases on the configurable attribute dropdown. This fixes a bug introduced in PR magento#17695 as detailed on issue magento#22270
@m2-assistant
Copy link

m2-assistant bot commented Apr 29, 2019

Hi @amol2jcommerce. 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

@dmytro-ch
Copy link
Contributor

@magento-engcom-team give me test instance

@magento-engcom-team
Copy link
Contributor

Hi @dmytro-ch. Thank you for your request. I'm working on Magento instance for you

@magento-engcom-team
Copy link
Contributor

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

@magento-engcom-team
Copy link
Contributor

Hi @dmytro-ch, thank you for the review.
ENGCOM-4842 has been created to process this Pull Request

@VasylShvorak
Copy link
Contributor

✔️ QA passed

@m2-assistant
Copy link

m2-assistant bot commented May 6, 2019

Hi @amol2jcommerce, 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 May 6, 2019
@magento-engcom-team magento-engcom-team added this to the Release: 2.2.9 milestone May 6, 2019
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