It would be a great feature to have an indication of where queue items came from?
If a queue item came from a rss feed called "reliable" or a rss feed called "unreliable" (simple case of only 2 rss feeds defined I have many more).
If the item did not come from a rss it could be flagged as api or manual add.
I can then use this source information to decide what to resume and what to delete from the paused state in the queue.
If this same information can then also appear in the History that would be very useful.
More details of where queue items came from?
Re: More details of where queue items came from?
The source is already listed in the download summary (click on History item).
When the NZB is coming directly from a website's API (through RSS), a URL will be listed as source.
Otherwise the local path will be listed.
When the NZB is coming directly from a website's API (through RSS), a URL will be listed as source.
Otherwise the local path will be listed.
Re: More details of where queue items came from?
Thanks but it was particularly when the item is in the queue that I would find this useful so I can make the decision before the item is processed.
For my RSS setup it would also be helpful if it included the RSS name (this means you know what search matched what from the same source).
Just the source URL in the queue would be better than nothing.
For my RSS setup it would also be helpful if it included the RSS name (this means you know what search matched what from the same source).
Just the source URL in the queue would be better than nothing.
Re: More details of where queue items came from?
Oh, you want to see it while still in the queue?
Hmm, could be done, but only conveniently in the file overview of a job.
I don't feel like stuffing in the queue line or the popup, because few people will be interested in it.
I'll have a look at it, but be aware that the to-do queue is large.
Hmm, could be done, but only conveniently in the file overview of a job.
I don't feel like stuffing in the queue line or the popup, because few people will be interested in it.
I'll have a look at it, but be aware that the to-do queue is large.