Serhii Dzhepa

This ticket was created by an internal Adobe team and was exported to the public GitHub as this issue. Later internal Jira ticket was closed as canceled. > After discussion...

@magento run all tests

Hello @ihor-sviziev @jayankaghosh Sorry for the late response. Let me please clarify the situation. We are working(fix, covering, QA, delivery, etc) and focusing on the Hight Priority(P0-P1-P2) tickets first. This...

Hello @kassner and @ihor-sviziev I have discussed this issue with our Security Team. **Short answer:** 1. Mentioned patches are not applicable for the 2.4.5. (_applicable only >> • The vulnerability...

@magento create issue

Hello @convenient and @ihor-sviziev Thank you for pointing out this situation! Unfortunately, I do not have a clear and transparent answer to "Why did it happen?" But I agree it...

Hello @achatpc I am not sure but it looks like a known issue. Could you please check this article and confirm if it helps? https://support.magento.com/hc/en-us/articles/8214752983949

@engcom-Bravo @engcom-November @engcom-Hotel Is it an issue related to Magento Core code or to the data-migration tool? If it's related to the tool(fix should be in tool repo) it makes...

Hello @amine-y and @ihor-sviziev Thank you for raising this issue! I do not know the reason but looks like this PR was missed because the related issue was closed: https://github.com/magento/magento2/issues/13952...

Hello @vinayshah Thank you for feedback and your proposal! Based on the description and label `feature request` the issue has been transferred to [Magento Feature Request](https://github.com/magento/community-features) public repo.