Closed martasiewierskastanczak closed 5 years ago
Hi @martasiewierskastanczak. Thank you for your report. To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento-engcom-team give me $VERSION instance
where $VERSION
is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.
@martasiewierskastanczak do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
@magento-engcom-team give me 2.2.6 instance
Hi @martasiewierskastanczak. Thank you for your request. I'm working on Magento 2.2.6 instance for you
Hi @martasiewierskastanczak, here is your Magento instance.
Admin access: http://34.228.235.121/i-19064-2-2-6//admin
Login: admin
Password: 123123q
Instance will be terminated in up to 3 hours.
Hi @engcom-backlog-nazar. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
[x] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).Details
If the issue has a valid description, the label Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.
[x] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description
label to the issue by yourself.
[x] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.3-develop
branchDetails
- Add the comment @magento-engcom-team give me 2.3-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.3-develop
branch, please, add the label Reproduced on 2.3.x
.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[x] 5. Verify that the issue is reproducible on 2.2-develop
branch. Details
- Add the comment @magento-engcom-team give me 2.2-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.2-develop
branch, please add the label Reproduced on 2.2.x
[x] 6. Add label Issue: Confirmed
once verification is complete.
[x] 7. Make sure that automatic system confirms that report has been added to the backlog.
@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-96137
, MAGETWO-96138
were created
I can confirm this is still an issue on 2.3.1
Hello @martasiewierskastanczak @vseager
Thank you for contribution and collaboration!
The corresponding internal ticket MAGETWO-96137
, MAGETWO-96138
were fixed and closed by Magento team
Delivered to 2.3-develop
branch and should be available with 2.3.2 release
Please see details in the next commits:
Delivered to 2.2-develop
branch and should be available with 2.2.9 release
Please see details in the next commits:
This issue didn't resolve in 2.3.2 as well. We are using Indian Rupee, and 1 extension that ADD Extra Service Charge(Collection Charge) during Checkout. Now if Order is above Rs.500, the discount applies on Cart Rule. The Checkout shows correct data but it doesn't load to paypal gateway, giving same issue as posted here.
Preconditions
Steps to reproduce
Expected result
Actual result