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

[Feature] Manual Control Over Watch Activity #3680

Closed
AdultSun opened this issue Apr 25, 2023 · 1 comment · Fixed by #4532
Closed

[Feature] Manual Control Over Watch Activity #3680

AdultSun opened this issue Apr 25, 2023 · 1 comment · Fixed by #4532

Comments

@AdultSun
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Currently, all watch activity metrics are tracked automatically. You can turn tracking on/off and adjust the watch percentage for the play counter, but everything else is handled automatically. There is no easy way to manually modify any of these metrics.

The current monitoring method is imperfect. I would like to manually input watch history that pre-dated the feature, but there is no way to do that in the UI. I would also like to track plays over DLNA, but those are not monitored currently and, again, I cannot manually track those plays within Stash either.

Describe the solution you'd like
Users should be able to manually modify or reset the last viewed date, play counter, play duration, and progress tracker. These values should be exposed to the edit panel where they can be changed or reset as needed.

I will also create a separate issue for DLNA tracking.

Describe alternatives you've considered
I guess I could edit the database directly but that's asking too much of the average user.

@randemgame
Copy link
Contributor

Another vote for being able to edit play history stuff manually. There's so many use cases when I'm watching stuff outside of Stash. I went into more detail in this request #3392

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

Successfully merging a pull request may close this issue.

2 participants