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 : Incorrect Data on Magento 2 Dashboard #38841

Closed
1 of 5 tasks
nylanBCM opened this issue Jun 19, 2024 · 14 comments
Closed
1 of 5 tasks

Issue : Incorrect Data on Magento 2 Dashboard #38841

nylanBCM opened this issue Jun 19, 2024 · 14 comments
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.5-p3 Indicates original Magento version for the Issue report.

Comments

@nylanBCM
Copy link

Preconditions and environment

  • Magento 2 ver. 2.4.5-p3
  • Go to the dashboard section

Steps to reproduce

  1. Log in to the Magento 2 admin dashboard.
  2. Navigate to the dashboard section where sales data is displayed.
  3. Observe the details beside the graph/chart.
  4. The dashboard of my Magento 2 store is displaying incorrect data.
  5. While the graph/chart shows previous sales, the day, and the time correctly, the detailed information beside the graph is nonsensical and unrelated to the actual sales data.

Mageto 2 Support

Expected result

The dashboard should accurately display, regarding of the actual sales :

  1. Daily revenue
  2. Tax
  3. Shipping fees
  4. Quantity of orders

Actual result

The details beside the sales graph/chart are incorrect and do not reflect the actual sales data. And I don't understand how they even calculate the revenue below the graph.

Additional information

No response

Release note

Could you please provide guidance or a fix to configure the dashboard to accurately display:

  1. Daily revenue
  2. Tax
  3. Shipping fees
  4. Quantity of orders

Triage and priority

  • 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”.
Copy link

m2-assistant bot commented Jun 19, 2024

Hi @nylanBCM. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

Copy link

m2-assistant bot commented Jun 19, 2024

Hi @engcom-Bravo. 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).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. 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!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.5-p3 Indicates original Magento version for the Issue report. label Jun 19, 2024
Copy link

m2-assistant bot commented Jun 20, 2024

Hi @engcom-Dash. 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).
    1. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
    1. Add Area: XXXXX label to the ticket, indicating the functional areas 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!

@engcom-Dash
Copy link
Contributor

@magento give me 2.4-develop instance

Copy link

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

Copy link

@engcom-Dash
Copy link
Contributor

Hi @nylanBCM

Thanks for reporting and collaboration.

Verified the issue on Magento 2.4 dev instance but the issue is not reproducible.

We are able to see the correct data on Magento 2 Dashboard

Steps to reproduce :

  1. Log in to the Magento 2 admin dashboard.
  2. Navigate to the dashboard section where sales data is displayed.
  3. Observe the details beside the graph/chart.
  4. The dashboard of my Magento 2 store is displaying incorrect data.
  5. While the graph/chart shows previous sales, the day, and the time correctly, the detailed information beside the graph is nonsensical and unrelated to the actual sales data.

Please refer the attached screenshots.

Previous data:

38841_1 38841_2

Date after new order is placed and order status is completed.

38841_3

@engcom-Dash engcom-Dash added the Issue: needs update Additional information is require, waiting for response label Jun 20, 2024
@nylanBCM
Copy link
Author

nylanBCM commented Jun 21, 2024 via email

@nylanBCM
Copy link
Author

I'm encountering an issue with the revenue calculation on my Magento 2.4.5-p3 dashboard. The displayed revenue for "today" does not accurately reflect sales from 12 AM to the current time, instead using an incorrect period, resulting in inaccurate daily revenue reporting. I've confirmed the timezone and locale settings are correct, but the problem persists. Could anyone advise on how to modify the code to ensure the correct time range is used for daily revenue calculations, or suggest any solutions or extensions that might help?

@engcom-Dash
Copy link
Contributor

@magento give me 2.4-develop instance

Copy link

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

Copy link

Copy link

m2-assistant bot commented Jul 31, 2024

Hi @engcom-Delta. 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).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. 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!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Bravo
Copy link
Contributor

Hi @nylanBCM,

Thanks for your update.

We have verified the issue in Latest 2.4-develop instance and the issue is not reproducible.It is recommended to verify the issues in Latest 2.4-develop instance.Hence we are closing the issue.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.5-p3 Indicates original Magento version for the Issue report.
Projects
None yet
Development

No branches or pull requests

4 participants