JMO

not only do we not develop sabnzbd app itself, but this is all the more amusing given that you can easily change back to the old webui anyways. Hardly the point, is it. Feedback is feedback, just in this case it was misplaced. I've been enlightened as to the development process, that should have been sufficient enough a response.

Are you actually being serious?! You know we don't develop sabnzbd right? We just package it into a docker. From what I understand your complaints are to do with the updated sabnzbd webui, so would be far better placed directed at the sabnbzd developer. As linked in the first post. Clearly I was not aware of that. I'm not a programmer. I have no idea what the process of docker development, or app development for that matter, is. I'll take the feedback where it belongs.

Linuxserver (and all docker template maintainers for that matter) do not write the actual app themselves. They merely package it. This would need to be posted on Sab's forum. You can get to their page by hitting "Project Page" from within CA on the app Thanks for the information.

Hi, I suppose this thread is as good as any for posting feedback on this container. I've switched from Needo's SAB to try this out and while the process has been fairly painless, and the updated interface is somewhat refreshing, I do have a some criticisms of the overall UI. In general, the UI is pretty good, however there are a few issues that I have found bothersome: 1. Status and interface options>Web Interface. We may only have one extra queue column. This feels pretty arbitrary and I find it actually quite annoying. I like to see both the "category" and "priority" columns, but now I can't. 2. The multi-operations button (and subsequently, the means by which job priorities are changed). Earlier I had occasion to change the priority of 12 episodes of a television series. I clicked multi-operations to bring up the check-boxes, scrolled back up my queue (because bringing up the check-boxes dumps you to the bottom of the page), selected my episodes, scrolled back down, changed priority to high. Bob's your uncle. Too many steps, too much moving up and down the page. Additionally, I had the misfortune to click the check all button while I was just scrolling around the bottom of the page...which then set ALL my jobs to high priority. It was a learning experience that highlights another issue... 3. The priority dropdown box. If you use the multi-operation dropdown at the bottom of the page to change some job priorities and then wish to change some other jobs to different priorities you have to go to the top of the page, click the multi-operation button (to remove the check-boxes), click it again to bring them back, set the job priority, scroll back up and select the jobs. After which you then have to remember to click the multi-operations button to remove the check-boxes (or you can manually deselect all the jobs you just changed priority for)...just to be safe. 4. No text box to filter jobs. It is needed. 5. Why is job management split between the footer and header of the page? I've alluded to it already, having the functional parts of the multi-operations at the bottom of the page feels like bad design. Having said all that, it may be that there is functionaality that I have not quite discovered yet, or a workflow that I've not quite gotten used to that is detracting from my experience, so feel free to reply with suggestions . Please take these comments as constructive criticism. I am very appreciative of the work that the Linuxserver.io team puts into the docker community. Regards.