sdzhepa

sdzhepa

Member Since 8 years ago

@magento,

Experience Points
3
follower
Lessons Completed
1
follow
Lessons Completed
4
stars
Best Reply Awards
13
repos

42 contributions in the last year

Pinned
⚡ Magento2 Functional Testing Framework
⚡ Generate a TOC in markdown file
Activity
Oct
14
2 days ago
Activity icon
issue

sdzhepa issue comment magento/magento2

sdzhepa
sdzhepa

JS error in console on checkout when recaptcha for checkout/placing order is not enabled

Preconditions (*)

  1. Magento 2.4.3
  2. 'Stores > Configuration > Security > Google reCAPTCHA Storefront > Storefront > Enable for Checkout/Placing Order' set to 'No' (that's the default config)

Steps to reproduce (*)

  1. Add a product to cart
  2. Go to checkout
  3. Open element inspector, see the JS error

Expected result (*)

  1. No JS errors on checkout
  2. Besides not wanting to run into errors, I wouldn't expect checkout to load any recaptcha JS when all the recaptcha options are not enabled.

Actual result (*)

  1. Error message from recaptcha JS:
knockout.js:3753 Uncaught TypeError: Unable to process binding "afterRender: function(){return renderReCaptcha() }"
Message: Cannot read property 'rendering' of undefined
    at UiClass.initCaptcha (reCaptcha.js:117)
    at UiClass.renderReCaptcha (reCaptcha.js:182)
    at afterRender (eval at createBindingsStringEvaluator (knockout.js:3221), <anonymous>:3:134)
    at init (after-render.js:17)
    at knockout.js:3730
    at Object.ignore (knockout.js:1563)
    at knockout.js:3729
    at Object.arrayForEach (knockout.js:168)
    at applyBindingsToNodeInternal (knockout.js:3715)
    at applyBindingsToNodeAndDescendantsInternal (knockout.js:3573)

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

ps. I think severity should be higher, because any dev working om checkout will spot this, and will be looking for a fix. (I first checked all of my modules, themes and 3rd party modules: it's time consuming.)

Activity icon
issue

sdzhepa issue comment magento/magento2

sdzhepa
sdzhepa

JS error in console on checkout when recaptcha for checkout/placing order is not enabled

Preconditions (*)

  1. Magento 2.4.3
  2. 'Stores > Configuration > Security > Google reCAPTCHA Storefront > Storefront > Enable for Checkout/Placing Order' set to 'No' (that's the default config)

Steps to reproduce (*)

  1. Add a product to cart
  2. Go to checkout
  3. Open element inspector, see the JS error

Expected result (*)

  1. No JS errors on checkout
  2. Besides not wanting to run into errors, I wouldn't expect checkout to load any recaptcha JS when all the recaptcha options are not enabled.

Actual result (*)

  1. Error message from recaptcha JS:
knockout.js:3753 Uncaught TypeError: Unable to process binding "afterRender: function(){return renderReCaptcha() }"
Message: Cannot read property 'rendering' of undefined
    at UiClass.initCaptcha (reCaptcha.js:117)
    at UiClass.renderReCaptcha (reCaptcha.js:182)
    at afterRender (eval at createBindingsStringEvaluator (knockout.js:3221), <anonymous>:3:134)
    at init (after-render.js:17)
    at knockout.js:3730
    at Object.ignore (knockout.js:1563)
    at knockout.js:3729
    at Object.arrayForEach (knockout.js:168)
    at applyBindingsToNodeInternal (knockout.js:3715)
    at applyBindingsToNodeAndDescendantsInternal (knockout.js:3573)

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

ps. I think severity should be higher, because any dev working om checkout will spot this, and will be looking for a fix. (I first checked all of my modules, themes and 3rd party modules: it's time consuming.)

sdzhepa
sdzhepa

@engcom-November Could you please check it on the 2.4.3-p1 release? (it is the lates release)

Oct
13
3 days ago
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

JS error in console on checkout when recaptcha for checkout/placing order is not enabled

Preconditions (*)

  1. Magento 2.4.3
  2. 'Stores > Configuration > Security > Google reCAPTCHA Storefront > Storefront > Enable for Checkout/Placing Order' set to 'No' (that's the default config)

Steps to reproduce (*)

  1. Add a product to cart
  2. Go to checkout
  3. Open element inspector, see the JS error

Expected result (*)

  1. No JS errors on checkout
  2. Besides not wanting to run into errors, I wouldn't expect checkout to load any recaptcha JS when all the recaptcha options are not enabled.

Actual result (*)

  1. Error message from recaptcha JS:
knockout.js:3753 Uncaught TypeError: Unable to process binding "afterRender: function(){return renderReCaptcha() }"
Message: Cannot read property 'rendering' of undefined
    at UiClass.initCaptcha (reCaptcha.js:117)
    at UiClass.renderReCaptcha (reCaptcha.js:182)
    at afterRender (eval at createBindingsStringEvaluator (knockout.js:3221), <anonymous>:3:134)
    at init (after-render.js:17)
    at knockout.js:3730
    at Object.ignore (knockout.js:1563)
    at knockout.js:3729
    at Object.arrayForEach (knockout.js:168)
    at applyBindingsToNodeInternal (knockout.js:3715)
    at applyBindingsToNodeAndDescendantsInternal (knockout.js:3573)

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

ps. I think severity should be higher, because any dev working om checkout will spot this, and will be looking for a fix. (I first checked all of my modules, themes and 3rd party modules: it's time consuming.)

Oct
12
4 days ago
Activity icon
issue

sdzhepa issue comment magento/magento2

sdzhepa
sdzhepa

[Issue] Update AddDataForIndia.php

This issue is automatically created based on existing pull request: magento/magento2#33172: Update AddDataForIndia.php


Added Ladakh Union Territory, Reference: https://en.wikipedia.org/wiki/Ladakh

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes magento/magento2#<issue_number>

Manual testing scenarios (*)

  1. ...
  2. ...

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)
Sep
23
3 weeks ago
Activity icon
issue

sdzhepa issue comment magento/magento2

sdzhepa
sdzhepa

JS error in console on checkout when recaptcha for checkout/placing order is not enabled

Preconditions (*)

  1. Magento 2.4.3
  2. 'Stores > Configuration > Security > Google reCAPTCHA Storefront > Storefront > Enable for Checkout/Placing Order' set to 'No' (that's the default config)

Steps to reproduce (*)

  1. Add a product to cart
  2. Go to checkout
  3. Open element inspector, see the JS error

Expected result (*)

  1. No JS errors on checkout
  2. Besides not wanting to run into errors, I wouldn't expect checkout to load any recaptcha JS when all the recaptcha options are not enabled.

Actual result (*)

  1. Error message from recaptcha JS:
knockout.js:3753 Uncaught TypeError: Unable to process binding "afterRender: function(){return renderReCaptcha() }"
Message: Cannot read property 'rendering' of undefined
    at UiClass.initCaptcha (reCaptcha.js:117)
    at UiClass.renderReCaptcha (reCaptcha.js:182)
    at afterRender (eval at createBindingsStringEvaluator (knockout.js:3221), <anonymous>:3:134)
    at init (after-render.js:17)
    at knockout.js:3730
    at Object.ignore (knockout.js:1563)
    at knockout.js:3729
    at Object.arrayForEach (knockout.js:168)
    at applyBindingsToNodeInternal (knockout.js:3715)
    at applyBindingsToNodeAndDescendantsInternal (knockout.js:3573)

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

ps. I think severity should be higher, because any dev working om checkout will spot this, and will be looking for a fix. (I first checked all of my modules, themes and 3rd party modules: it's time consuming.)

sdzhepa
sdzhepa

Hello @hostep @mrtuvn @glevhen

Let me try to shade more lite on the issue based on communication and collaboration in the internal Jira ticket.

  • recently Jira ticket related to this public report was taken into the sprint scope by one of the internal teams
  • But on the initial phase, a QA engineer was not able to reproduce this issue on the latest 2.4-develop branch with security-package installed
  • also issue cannot be reproduced on the 2.4.3-p1

Based on such verification, the ticket was closed by QA with the resolution "cannot reproduce" - according to workflow. It looks like the problem was already fixed in the scope of some other PRs/commits/tasks etc.

If you still experience a similar issue on the latest version of code I would recommend opening a new issue with updated versions/steps and actual/expected results

Sep
21
3 weeks ago
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

Wrong default permissions after composer install

I believe that there is a problem with the permissions set by many modules. I checked some of our productions platform this morning and they all have this permission problem.

And setting the permissions with the find command as documented will only fix the group permissions, not the permissions for other users.

Preconditions

  1. magento 2.3.4 composer installation

Steps to reproduce

  1. Check that you umask is correct, otherwise set it to distribution default: $ umask 0002 $ umask 0002
  2. composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition

Expected result

  1. No file should be world writable. The following command in the project should return no result: find -perm -o+w -not -type l

Actual result

  1. $ find -perm -o+w -not -type l | wc -l 45415

Sample file with wrong permissions: -rw-rw-rw- 1 x2i www-data 1370 Feb 4 10:28 vendor/magento/magento2-base/index.php

Sample file with good permissions: -rw-r--r-- 1 x2i www-data 2378 Feb 4 2020 .vendor/magento/zendframework1/library/Zend/Date/DateObject.php

Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

Wrong default permissions after composer install

I believe that there is a problem with the permissions set by many modules. I checked some of our productions platform this morning and they all have this permission problem.

And setting the permissions with the find command as documented will only fix the group permissions, not the permissions for other users.

Preconditions

  1. magento 2.3.4 composer installation

Steps to reproduce

  1. Check that you umask is correct, otherwise set it to distribution default: $ umask 0002 $ umask 0002
  2. composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition

Expected result

  1. No file should be world writable. The following command in the project should return no result: find -perm -o+w -not -type l

Actual result

  1. $ find -perm -o+w -not -type l | wc -l 45415

Sample file with wrong permissions: -rw-rw-rw- 1 x2i www-data 1370 Feb 4 10:28 vendor/magento/magento2-base/index.php

Sample file with good permissions: -rw-r--r-- 1 x2i www-data 2378 Feb 4 2020 .vendor/magento/zendframework1/library/Zend/Date/DateObject.php

Activity icon
issue

sdzhepa issue comment magento/magento2

sdzhepa
sdzhepa

Wrong default permissions after composer install

I believe that there is a problem with the permissions set by many modules. I checked some of our productions platform this morning and they all have this permission problem.

And setting the permissions with the find command as documented will only fix the group permissions, not the permissions for other users.

Preconditions

  1. magento 2.3.4 composer installation

Steps to reproduce

  1. Check that you umask is correct, otherwise set it to distribution default: $ umask 0002 $ umask 0002
  2. composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition

Expected result

  1. No file should be world writable. The following command in the project should return no result: find -perm -o+w -not -type l

Actual result

  1. $ find -perm -o+w -not -type l | wc -l 45415

Sample file with wrong permissions: -rw-rw-rw- 1 x2i www-data 1370 Feb 4 10:28 vendor/magento/magento2-base/index.php

Sample file with good permissions: -rw-r--r-- 1 x2i www-data 2378 Feb 4 2020 .vendor/magento/zendframework1/library/Zend/Date/DateObject.php

Sep
14
1 month ago
pull request

sdzhepa merge to magento/magento2

sdzhepa
sdzhepa

Reinstate disposition header for email messages

Description (*)

This pull request reverts the work-around introduced temporarily as part of #25076 and changes the minimum required version of upstream package laminas/lamnias-mail to fix the actual problem identified in #25076. External package has already been updated to fix the bug in https://github.com/magento/magento2/commit/5498e7613e51288184f1c1e5a6368544efa4b7bb.

Related Pull Requests

Fixed Issues (if relevant)

Manual testing scenarios (*)

  1. Generate an email from Magento (eg, new user welcome, sale order success)
  2. Observe headers in email

Questions or comments

None

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)
Sep
13
1 month ago
Activity icon
issue

sdzhepa issue comment magento/magento2

sdzhepa
sdzhepa

Reinstate disposition header for email messages

Description (*)

This pull request reverts the work-around introduced temporarily as part of #25076 and changes the minimum required version of upstream package laminas/lamnias-mail to fix the actual problem identified in #25076. External package has already been updated to fix the bug in https://github.com/magento/magento2/commit/5498e7613e51288184f1c1e5a6368544efa4b7bb.

Related Pull Requests

Fixed Issues (if relevant)

Manual testing scenarios (*)

  1. Generate an email from Magento (eg, new user welcome, sale order success)
  2. Observe headers in email

Questions or comments

None

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)
Aug
26
1 month ago
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

Changed repository name of one of the composer.lock included packages.

In the composer.lock file in current Magento 2 codebase we can find module named allure-framework/allure-php-api which has source on <https://github.com/allure-framework/allure-php-commons.git>

According to this commit repository name has been changed leading to crash every Magento 2 application failing caused by not existing source.

 

  - Installing allure-framework/allure-php-api (1.1.8): Downloading (connecting...).................Downloading (0%) ............ Failed to download allure-framework/allure-php-api from dist: The "https://codeload.github.com/allure-framework/allure-php-commons/legacy.zip/<hash>" file could not be downloaded (HTTP/1.1 404 Not Found) Now trying to download from source - Installing allure-framework/allure-php-api (1.1.8): Failed to update https://github.com/allure-framework/allure-php-commons.git in cache, package installation for allure-framework/allure-php-api might fail. Cloning <hash> from cache <hash> is gone (history was rewritten?)
Aug
24
1 month ago
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] testing new confirmation flow 004

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] Triage Test Issue 02

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Aug
19
1 month ago
Activity icon
issue

sdzhepa issue comment magento/magento2

sdzhepa
sdzhepa

Upgrade Issue, While upgrade from Magento 2.4.2-p1 to Magento 2.4.3

Preconditions (*)

  1. Magento 2.4.3 (EE)
  2. Composer 2

Steps to reproduce (*)

Hi,

I am upgrading from Magento 2.4.2-p1 from Magento 2.4.3. Composer Update was working fine, but when I tried to run

php bin/magento setup:upgrade

I am getting the below error.

Unable to apply data patch Magento\Paypal\Setup\Patch\Data\UpdateBmltoPayLater for module Magento_Paypal. Original exception message: Notice: Undefined offset: 1 in vendor/magento/module-paypal/Setup/Patch/Data/UpdateBmltoPayLater.php on line 138 When I checked the code, I found out we didn't check whether the value is exploadable in some scenarios like this

path => payment/paypal_express_bml/active , value => 0

and it's throwing the error in this line

$page = $settingParts[0]; $setting = $settingParts[1];

Expected result (*)

While Setup:upgrade it should work fine

Actual result (*)

Module 'Magento_Paypal': Unable to apply data patch Magento\Paypal\Setup\Patch\Data\UpdateBmltoPayLater for module Magento_Paypal. Original exception message: Notice: Undefined offset: 1 in vendor/magento/module-paypal/Setup/Patch/Data/UpdateBmltoPayLater.php on line 138

Fix for this : Add if(strpos($setting, '_') == false) { continue }

foreach ($bmlSettings as $bmlPath => $bmlValue) { $setting = str_replace(self::BMLPATH, '', $bmlPath); if(strpos($setting, '_') == false) { continue; }

sdzhepa
sdzhepa

Hello

Let me try to bring some light on this issue. Right not in internal Jira, there are two tickets linked with this issue

  1. AC-493
  • Status: Fixed/Done
  • Target version: 2.4.4 (means should be available in 2.4.4 release)
  • related commits can be found by search using AC-493 in commits: EXAMPLE
  1. AC-507
  • Status: Open/Ready for Dev
  • Target version: 2.4.3-p1

cc: @drinkingsouls @ntoombs19 @fahu @sims-smith-corona @EmperorKonstantin @fascinosum @ericclaeren @ihor-sviziev @hostep

Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

Call to a member function getId() on array in module-sales/view/adminhtml/templates/order/totals/tax.phtml:62

Preconditions (*)

  1. Magento Version 2.4.0

Steps to reproduce (*)

  1. Go to Store -> Configuration -> Sales -> Tax -> Orders, Invoices, Credit Memos Display Settings -> Display Full Tax Summary and change to YES
  2. Go to Sales -> Orders -> Open Order -> Invoice Tab -> Open Invoice -> Page View Source -> Issue will Visible at the end of view source Page

Expected result (*)

  1. <Screenshots, logs or description]
  2. Screenshot 2020-09-17 at 9 54 45 PM
  3. $rate->getId() should be like $rate['id']

4.Screenshot 2020-09-17 at 9 57 24 PM need to expand this array and add id as key to get in the result to the Magento\Tax\Model\ResourceModel\Calculation Screenshot 2020-09-17 at 9 59 34 PM add the ID CONST in the Magento\Tax\Model\Sales\Order\Tax class

Actual result (*)

  1. [Screenshots, logs or description]
Screenshot 2020-09-17 at 10 00 56 PM

Additional info from Engcom

Switch Magento into Developer mode to reproduce the issue bin/magento dep:mo:set developer The invoice looks like this html_invoice

Error from View Page Source Selection_017

Activity icon
issue

sdzhepa issue comment magento/magento2-page-builder

sdzhepa
sdzhepa

Column group story

Description (*)

Story

Bug

Task

Fixed Issues (if relevant)

  1. Fixes magento/magento2-page-builder#754: Introduce Column Groups
  2. Fixes magento/magento2-page-builder#749: User can move Column Group on stage
  3. Fixes magento/magento2-page-builder#748: Configure rules for columns
  4. Fixes magento/magento2-page-builder#747: User can delete columns from the column group except the last one
  5. Fixes magento/magento2-page-builder#751: Move grid size setting to settings panel

Builds

Related Pull Requests

Manual testing scenarios (*)

  1. ...
  2. ...

Questions or comments

Checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)
Aug
18
1 month ago
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] Triage Test Issue 01

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] Triage Test Issue 01

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] testing new confirmation flow 004

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] testing new confirmation flow 003

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Aug
17
1 month ago
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] testing new confirmation flow 003

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] testing new confirmation flow 003

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] testing new confirmation flow 003

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] testing new confirmation flow 002

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] testing new confirmation flow 002

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] testing new confirmation flow 002

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] testing new confirmation flow 001

Preconditions (*)

  • Point 1
  • Point 2
  • Point 3

{ )(*&^%$#<?

Code section

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Activity icon
issue

sdzhepa issue magento/magento2

sdzhepa
sdzhepa

[TEST] testing new confirmation flow 001

Preconditions (*)

  • Point 1
  • Point 2
  • Point 3

{ )(*&^%$#<?

Code section

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description]

Actual result (*)

  1. [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”.
Previous