| Project |
Feature |
Score |
Description |
| tidusjar/Ombi |
Modularization |
2 |
I'm not sure how many of you use ombi in conjunction with a web manager (organizr/idashboard/muximux) But giving guest access to a one of those and having ombi available is AMAZING. I personally have organizr along with guest tabs for plex, ombi, tumblr (an easy way to run a blog to make announcements, recommendations, or anything else i want to communicate to my users), and mattermost (a work in progress that is basically a self hosted slack clone, so i can keep track of all notifications, and users can get rss feeds that matter to them, along with the ability to chat with each other/me, I'm also working on routing all ombi user notifications through email-->ifttt-->mattermost so they can use it as their central hub for all notifications and never have to leave the domain). It all makes for a pretty professional looking webapp.
The one thing that is getting in the way of this beautiful workflow is jamie's insistence on building every god damn feature under the sun :)) OK, obviously that is amazing and I'm very grateful. BUT my request (and like most things i ask for, im not completely sure how this would play out exactly)
I'm wondering if there would be a way to (optionally) separate features in the future. So for example, I saw a request to add a tv calendar for upcoming tv shows. While this is again AWESOME, it is something i have been trying to get through trakt (though they would need to enable iframes for it to work with organizr) But as a separate tab in organizr. The same goes for a web based "newsletter", and anything else that isn't specifically part of the core "plex requests". It would even make sense to spin out "issues" and the landing page.
I understand this is not at all desirable to anyone that doesn't use a dashboard, but I'm putting this here to see if there are enough dashboard users, and if this "feature" is easy enough to incorporate that its considered. |
| Tautulli/Tautulli |
Instead of viewing history for "ALL" users or 1 specific user, let us view history for all users EXCEPT 1 or 2. |
3 |
Basically I would like to see the history page EXCLUDING 1 or 2 power users. That info would be much more useful to me. I think the easiest way would be to have check boxes next to each user in the drop down, so we could either enable or disable each user individually from showing up in the history. |
| tidusjar/Ombi |
Sub-Zero integration |
4 |
Pretty much all my "issues" are missing subtitles. Would be great if i could just handle that in ombi instead of having to go out to SZ to deal with it and then come back to mark the issue resolved.
Based on this discussion: https://www.reddit.com/r/PleX/comments/5smq2s/rplexs_tool_tuesday_thread_20170207_subzero/ddgzds3/ |
| tidusjar/Ombi |
LazyLibrarian Support |
39 |
I've seen this come up, but i can't remember if Jamie has made a ruling on it :) Since ombi is no longer plex only, i would REALLY love to see LL support. I would never give users access to sonarr/radarr, and the same is true of LL, so ombi really would be the missing f-ing link! It gets a bad rap, but ebook automation does work! It just desperately needs a front end for users. Plus this could just be turned off like music, and wouldn't get in anyone's way if they didn't want it. |
| causefx/Organizr |
Ombi Media Row |
3 |
I propose a third (optional) media row dedicated to ombi. I don't think this would work without ombi sso support, but im hopping that once thats in place it will be possible to tie ombi user info to org. The result im looking for is to get a personalized row of media per user that shows their own requests, with some kind of indicator overlay that shows whether the title was accepted/rejected/fulfilled/pending, and a filter button to sort through those options. |
| causefx/Organizr |
Per user CSS and HTML |
2 |
I think this would actually solve a TON of other low level feature requests (at least 3 of the feathub requests too). Instead of having a drop down for "Minimum authentication level for homepage", that drop down should just have all the user profiles, 1 for guest, and 1 default so we could add different code for each individual user. If no custom html exists for a user, it defaults to... default. And then do the exact same thing for the custom css. This would allow us a lot of creative freedom. We could have different messages popup in different users home pages, you could hide tabs... or really anything (like the now playing section for example), from specific users, and so much more... I think we could get a lot of creative mileage out of this one |
| tidusjar/Ombi |
"Follow" a movie/show |
4 |
i think we need the ability to request something thats already been requested but i was thinking it would work better if it was a separate button (im thinking star icon) that basically "monitors" that title. It would do so independently of the request status, so u could even monitor something without requesting it (though not sure why u would do that) but this would make it so that ANYTHING that happens w that title gets u a notification... it gets accepted/rejected in ombi, added to plex, removed from plex, replaced w a different quality, subs added/modified, a new issue is reported/resolved, etc... all trigger a notification to whoever is "monitoring" it. |
| Flexget/Flexget |
NZBHydra Plugin |
1 |
I'm hoping an nzbhydra2 plugin would allow us to only need to configure 1 recipe for all indexers, instead of doing them one by one.
If you're unaware, https://github.com/theotherp/nzbhydra2 is a consolidation tool/meta search agent for all your indexers/trackers. Incredibly superior to dealing with them all one by one. |