test confirmation j status

sdzhepa commented 4 years ago

Preconditions (*)

1. 2.

Steps to reproduce (*)

1. 2.

Expected result (*)

[Screenshots, logs or description]

Actual result (*)

[Screenshots, logs or description]

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

[ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
[ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
[ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
[ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
[ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

m2-assistant[bot] commented 4 years ago

Hi @sdzhepa. Thank you for your report. To help us process this issue please make sure that you provided the following information:

Summary of the issue
Information on your environment
Steps to reproduce
Expected and actual results

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 give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

Join Magento Community Engineering Slack and ask your questions in #github channel.

:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

magento-engcom-team commented 4 years ago

:white_check_mark: Confirmed by @sdzhepa Thank you for verifying the issue. Based on the provided information internal tickets MC-37482 were created

Issue Available: @sdzhepa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

m2-assistant[bot] commented 4 years ago

Hi @sdzhepa. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
1. Verify that the issue is reproducible on 2.4-develop branch
  Details
  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
1. If the issue is not relevant or is not reproducible any more, feel free to close it.

Join Magento Community Engineering Slack and ask your questions in #github channel.

slavvka commented 4 years ago

@magento give me 2.4-develop instance with edition B2B without extension magento/inventory, magento/magento2-page-builder

magento-deployment-service[bot] commented 4 years ago

Hi @slavvka. Thank you for your request. I'm working on Magento instance for you.

magento-deployment-service[bot] commented 4 years ago

Hi @slavvka, here is your Magento Instance: https://3a245f856eeea238f78dc0b6573664d1-2-4-develop.instances.magento-community.engineering Admin access: https://3a245f856eeea238f78dc0b6573664d1-2-4-develop.instances.magento-community.engineering/admin_e143 Login: c227c2b8 Password: 7d48ca666145

slavvka commented 4 years ago

@magento give me 2.4-develop instance with edition B2B without extension magento/inventory

magento-deployment-service[bot] commented 4 years ago

Hi @slavvka. Thank you for your request. I'm working on Magento instance for you.

magento-deployment-service[bot] commented 4 years ago

Hi @slavvka, here is your Magento Instance: https://3a245f856eeea238f78dc0b6573664d1-2-4-develop.instances.magento-community.engineering Admin access: https://3a245f856eeea238f78dc0b6573664d1-2-4-develop.instances.magento-community.engineering/admin_b409 Login: 382346ce Password: c59117335ac7

slavvka commented 4 years ago

@magento give me 2.4 instance

magento-deployment-service[bot] commented 4 years ago

Hi @slavvka, unfortunately there is no ability to deploy 2.4 Magento instance. Please make sure you specify the correct Magento version/branch.

slavvka commented 4 years ago

@magento give me 2.4.0 instance

magento-deployment-service[bot] commented 4 years ago

Hi @slavvka. Thank you for your request. I'm working on Magento instance for you.

magento-deployment-service[bot] commented 4 years ago

Hi @slavvka, here is your Magento Instance: https://3a245f856eeea238f78dc0b6573664d1-2-4-0.instances.magento-community.engineering Admin access: https://3a245f856eeea238f78dc0b6573664d1-2-4-0.instances.magento-community.engineering/admin_28b6 Login: 7fdd1878 Password: 8164fbf81c82

magento-engcom-team commented 3 years ago

Hi @sdzhepa, @sdzhepa.

Thank you for your report and collaboration!

The related internal Jira ticket MC-37482 was closed as Complete.

The fix will be available with the upcoming 2.4.3 release.

magento / magento2