Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Issue] Fix typo which trigger performance bug #35417

Closed
5 tasks
m2-assistant bot opened this issue May 4, 2022 · 3 comments · Fixed by #35216
Closed
5 tasks

[Issue] Fix typo which trigger performance bug #35417

m2-assistant bot opened this issue May 4, 2022 · 3 comments · Fixed by #35216
Assignees
Labels
Area: Catalog Component: Catalog Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: done Release Line: 2.4 Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@m2-assistant
Copy link

m2-assistant bot commented May 4, 2022

This issue is automatically created based on existing pull request: #35216: Fix typo which trigger performance bug


Description

Fix typo which triggers bug when Category Products Count cannot be taken from catalog_category_product_index table

Manual testing scenarios

  1. Go to admin->catalog->category
  2. see products count on the category tree
  3. make sure category products count is correct

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)
@m2-assistant m2-assistant bot added Component: Catalog Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. labels May 4, 2022
@m2-community-project m2-community-project bot added this to Pull Request In Progress in High Priority Backlog May 4, 2022
@engcom-Charlie engcom-Charlie added Release Line: 2.4 Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels May 4, 2022
@github-jira-sync-bot github-jira-sync-bot removed the Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed label May 4, 2022
@github-jira-sync-bot
Copy link

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

@engcom-Charlie engcom-Charlie added Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Area: Catalog Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels May 4, 2022
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.magento.com/browse/AC-3003 is successfully created for this GitHub issue.

@m2-assistant
Copy link
Author

m2-assistant bot commented May 4, 2022

✅ Confirmed by @engcom-Charlie. Thank you for verifying the issue.
Issue Available: @engcom-Charlie, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Catalog Component: Catalog Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: done Release Line: 2.4 Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
3 participants