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

Performance ToolKit missing Invoices #21491

Closed
Stoyvo opened this issue Feb 27, 2019 · 6 comments
Closed

Performance ToolKit missing Invoices #21491

Stoyvo opened this issue Feb 27, 2019 · 6 comments
Labels
feature request Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Priority: P3 May be fixed according to the position in the backlog. Progress: done

Comments

@Stoyvo
Copy link

Stoyvo commented Feb 27, 2019

Preconditions (*)

  1. Magento 2.2.7 & 2.3.0
  2. Dev environment

Steps to reproduce (*)

  1. Run performance toolkit:
    bin/magento setup:performance:generate-fixtures -s setup/performance-toolkit/profiles/ce/medium.xml
  2. Open Admin panel
  3. Observe no invoices

Expected result (*)

  1. Invoices to be generated with Orders

Actual result (*)

  1. No Invoices generated

WHY THIS MATTERS

For large sites with many orders and invoices, the Admin Dashboard is horribly slow. This is caused by the query that calculates the lifetime sales total

Magento may have caught this if invoices were populated using the performance toolkit.

Though a slow admin dashboard is not the reported issue of this ticket, it is important that Magento populates as much order data as possible for realistic performance metrics.

@magento-engcom-team
Copy link
Contributor

Hi @Stoyvo. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

@Stoyvo do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
  • no

Sorry, something went wrong.

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Feb 27, 2019
@ghost ghost self-assigned this Feb 28, 2019
@magento-engcom-team
Copy link
Contributor

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

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • Next steps are available in case you are a member of Community Maintainers.

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

Sorry, something went wrong.

@ghost ghost added Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed feature request labels Feb 28, 2019
@ghost
Copy link

ghost commented Feb 28, 2019

Hi @Stoyvo thank you for you report, It will be processed faster if you move this to https://github.com/magento/community-features

@ghost ghost closed this as completed Feb 28, 2019
@Stoyvo
Copy link
Author

Stoyvo commented Feb 28, 2019

@engcom-backlog-nazar Not sure I understand. Am I to make a ticket there, linked to my pull request on this repo?

@ghost
Copy link

ghost commented Mar 1, 2019

@Stoyvo Yes you need to open issue there and create PR linked issue to this repo. like this -> magento/community-features#141

@Stoyvo
Copy link
Author

Stoyvo commented Mar 1, 2019

Thanks @engcom-backlog-nazar

magento/community-features#147

@sivaschenko sivaschenko added the Priority: P3 May be fixed according to the position in the backlog. label Oct 23, 2020
@ghost ghost added the Progress: done label Oct 23, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Priority: P3 May be fixed according to the position in the backlog. Progress: done
Projects
Archived in project
Development

No branches or pull requests

3 participants