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

Stats Traffic claimed no site traffic #88209

Closed
guarani opened this issue Mar 5, 2024 · 1 comment
Closed

Stats Traffic claimed no site traffic #88209

guarani opened this issue Mar 5, 2024 · 1 comment
Labels
[Feature] Stats Everything related to our analytics product at /stats/ Needs triage Ticket needs to be triaged [Pri] Low Address when resources are available. [Type] Bug

Comments

@guarani
Copy link
Contributor

guarani commented Mar 5, 2024

Quick summary

The Stats Traffic screen showed a "No data in this period" message when there was indeed traffic in that period.

CleanShot 2024-03-05 at 15 18 42@2x

Steps to reproduce

I couldn't reproduce this issue after first seeing it

What you expected to happen

  • Data should be shown for the period (or an error message shown explaining that data couldn't be fetched)
  • The bar chart shouldn't display bars if the data couldn't be fetched (either because there was an error or because there was no data)
  • The date forwards and backwards buttons could be disabled, because when the message is displayed, tapping them "clears" the bar chart bars

What actually happened

  • The screen said there was no data for the period when there was (it showed up after a pull-to-refresh)
  • The bar chart showed full bars despite data not being fetched or an error occurring
  • The backwards and forwards date buttons allowed me to navigate, resulting in an unexpected UI state

Impact

One

Available workarounds?

Yes, easy to implement

Platform (Simple and/or Atomic)

No response

Logs or notes

No response

@guarani guarani added [Type] Bug [Feature] Stats Everything related to our analytics product at /stats/ Needs triage Ticket needs to be triaged labels Mar 5, 2024
@github-actions github-actions bot added the [Pri] Low Address when resources are available. label Mar 5, 2024
@kangzj kangzj moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Mar 5, 2024
@jordesign
Copy link
Contributor

Given this impacted a single site, and there's no follow up or activity since May 2024 - I'll close this issue.

@jordesign jordesign closed this as not planned Won't fix, can't repro, duplicate, stale Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Stats Everything related to our analytics product at /stats/ Needs triage Ticket needs to be triaged [Pri] Low Address when resources are available. [Type] Bug
Development

No branches or pull requests

2 participants