Magento Community Engineering

Results 196 comments of Magento Community Engineering

:white_check_mark: Confirmed by @dmytro-ch Thank you for verifying the issue. Based on the provided information internal tickets `MC-33287` were created **Issue Available**: @dmytro-ch, _You will be automatically unassigned. Contributors/Maintainers can...

Hi @engcom-backlog-tomash. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go...

Hi @tomekjordan. Thank you for your report. To help us process this issue please make sure that you provided the following information: - [ ] Summary of the issue -...

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:...

@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets `MAGETWO-96277`, `MAGETWO-96278` were created

Hi @andparsons. Thank you for your request. I'm working on Magento 2.3-develop instance for you

Hi @andparsons, here is your [Magento instance](https://i-25189-2-3-develop.instances.magento-community.engineering). Admin access: [https://i-25189-2-3-develop.instances.magento-community.engineering/admin](https://i-25189-2-3-develop.instances.magento-community.engineering/admin) Login: `admin` Password: `123123q` Instance will be terminated in up to 3 hours.

@RakeshJesadiya, thank you for your report. We've acknowledged the issue and added to our backlog.

Hi @engcom-backlog-andrii. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go...

@engcom-backlog-tomash Thank you for verifying the issue. Unfortunately, not enough information was provided to created internal ticket. Please consider adding the following: - [ ] Update issue content to follow...