

Hi @eduard13. 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.
@eduard13 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
Hi @irajneeshgupta. 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:
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.
[x] 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_!
[ ] 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.
Hi @vasilii-b. 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:
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.
[x] 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_!
[ ] 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.
@irajneeshgupta Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97882 were created
@irajneeshgupta thank you for the confirmation. Does it really take 1 minute for you to reproduce the issue?
@irajneeshgupta thank you for the confirmation. Does it really take 1 minute for you to reproduce the issue?
@rogyar
yeah, i have local setup of dev-2.3-develop , it takes hardly 1 min to view an item and click on Customizable Options ->add options.
@eduard13
I assumed that it will take sometime to create PR of it.
@engcom-backlog-nazar
https://i-20487-2-3-develop.instances.magento-community.engineering/admin
all 2.3-develop instance are redirecting to 2.2-develop instance.
Hi @eduard13. Thank you for your report.
The issue has been fixed in magento/magento2#20498 by @eduard13 in 2.3-develop branch
Related commit(s):
The fix will be available with the upcoming 2.3.1 release.
@magento-engcom-team give me 2.2-develop instance
Hi @dmytro-ch. Thank you for your request. I'm working on Magento 2.2-develop instance for you
Hi @dmytro-ch, here is your Magento instance.
Admin access: https://i-20497-2-2-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.
Hi @eduard13. Thank you for your report.
The issue has been fixed in magento/magento2#20821 by @eduard13 in 2.2-develop branch
Related commit(s):
The fix will be available with the upcoming 2.2.9 release.
Most helpful comment
@irajneeshgupta thank you for the confirmation. Does it really take 1 minute for you to reproduce the issue?