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

Shows not showing imported historical stats #295

Open
nickdollimount opened this issue Jan 9, 2025 · 2 comments
Open

Shows not showing imported historical stats #295

nickdollimount opened this issue Jan 9, 2025 · 2 comments

Comments

@nickdollimount
Copy link

nickdollimount commented Jan 9, 2025

This has been an issue for me for a while through different versions but I'd really like to get this working so I figured I'd report it but my Jellystat won't display stats for my shows library in the 'Libraries' and the 'Statistics' sections. However, you can see data in the 'Activity' section, though there is a piece of information on all the shows that shows as '$nullEnull'.

Environment Details

  • OS: Ubuntu 24.10
  • Browser: Brave
  • Jellystat Version: 1.1.2
  • Jellyfin Version: 10.10.3

Steps to reproduce the behavior:

  1. Configure a new Jellystat instance
  2. Log into Jellystat
  3. Manually perform full import (automatic one fails)
  4. Import Playback Reporting Plugin Data
  5. Click Libraries tab on the left; no tracked information is listed for TV Shows
  6. Click Statistics tab on the left; no tracked information is listed for TV Shows
  7. Click Activity tab on the left; show watch information is listed

Expected behavior
Statistics information should be displayed for TV Shows library as it does for Movies library.

Screenshots
image
image
image

@nickdollimount
Copy link
Author

As an update, new playbacks appear to be showing. It's only the imported historic data that's not being displayed.

@nickdollimount nickdollimount changed the title Shows not showing stats Shows not showing imported historical stats Jan 9, 2025
@nicklausroach
Copy link

nicklausroach commented Jan 11, 2025

I think this is the same issue as described here: #249, there is a "solution" posted by running a few queries directly on the postgres db! That said this is definitely still an issue that needs to be handled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants