Pack Seed Time doesn't work for Whisparr #1016

New issue

Closed

opened 2026-02-20 10:06:23 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 10:06:23 -05:00

Owner

Originally created by @Simpuhl on GitHub (Feb 20, 2024).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

When adding a Pack Seed Time, it does not transfer to Whisparr.

Expected Behavior

It should go into "Season-Pack Seed Time" field.

Steps To Reproduce

Add Pack Seed Time to tracker that Whisparr uses

Environment

- OS: Synology
- Prowlarr: Latest
- Docker Install: Yes
- Using Reverse Proxy: No
- Browser: Edge

What branch are you running?

Master

Trace Logs?

Not needed

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @Simpuhl on GitHub (Feb 20, 2024). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior When adding a Pack Seed Time, it does not transfer to Whisparr. ### Expected Behavior It should go into "Season-Pack Seed Time" field. ### Steps To Reproduce Add Pack Seed Time to tracker that Whisparr uses ### Environment ```markdown - OS: Synology - Prowlarr: Latest - Docker Install: Yes - Using Reverse Proxy: No - Browser: Edge ``` ### What branch are you running? Master ### Trace Logs? Not needed ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [X] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman

2026-02-20 10:06:23 -05:00

closed this issue
added the
Type: Bug

Area: API

Priority: Low

Status: Needs Triage
labels

deekerman commented

2026-02-20 10:06:24 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Feb 21, 2024):

For future reference, please use the versions from System > Status since latest is not a version.

@mynameisbogdan commented on GitHub (Feb 21, 2024): For future reference, please use the versions from System > Status since `latest` is not a version.

deekerman commented

2026-02-20 10:06:24 -05:00

Author

Owner

@Simpuhl commented on GitHub (Feb 21, 2024):

For future reference, please use the versions from System > Status since latest is not a version.

My bad, its just when I pull I choose latest so I thought that was OK.

So is this a bug or something? I noticed you closed it, was it fixed or do you need me to add screenshot or anything else?

Again sorry for not putting correct information, just trying to help out to make the application better, if I knew C# I'd try to do it myself but I'm still learning how to even pull requests and all that here.

@Simpuhl commented on GitHub (Feb 21, 2024): > For future reference, please use the versions from System > Status since `latest` is not a version. My bad, its just when I pull I choose latest so I thought that was OK. So is this a bug or something? I noticed you closed it, was it fixed or do you need me to add screenshot or anything else? Again sorry for not putting correct information, just trying to help out to make the application better, if I knew C# I'd try to do it myself but I'm still learning how to even pull requests and all that here.

deekerman commented

2026-02-20 10:06:25 -05:00

Author

Owner

@Simpuhl commented on GitHub (Feb 21, 2024):

OK NM, I see where it says completed and the code changed.

Your awesome ty

@Simpuhl commented on GitHub (Feb 21, 2024): OK NM, I see where it says completed and the code changed. Your awesome ty