I'm sure that the devs use a proper bug tracker (and feature request tracker) -- please make it public so that we're aware of what's being worked on and which bugs/features are assigned to which milestone/release.
Please "Like This" here if you support this initiative ----------------------------------------------------------------->
I'm going to agree to this, especially in light of recent developments in here and in development in general.
Please don't make this public. The only thing it would do is to aggravate people who feel their pet bugs/features aren't getting the attention they think it deserves.
Multiple platform software development isn't easy and demanding more information, that isn't yours to demand in the first place, isn't going to magically make your issues go away. All it is going to do is give you more fuel to justify the way you feel.
Plex could show you the information they have in their internal planning/packaging tools but they can't control how you decide to interpret that information. Having an internal place to discuss features, bugs, their importance and priority means that developers and other Plex employees can be candid about those specific things.
It is intentionally ignorant to think that the Plex team is doing anything but working their ■■■■■ of on getting as many new features, bug fixes and dog pictures as they can.
Having paid paid for your Plex Pass doesn't mean you get to demand an ever increasing amount of things from the development team and Plex itself. It means that you paid for the features that were outlined https://plex.tv/subscription/welcomeon this page. They also went above and beyond that to create this forum section that allows you to have a voice in a discussion that might get more attention from the developers. It doesn't mean that you get to have a 1 on 1 discussion with Plex any time you decide that you want more than you have already.
Either the Plex Pass is worth it for you and you can continue paying it or it isn't and you can stop paying it.
I'm not sure if the internal bug tracker needs to be public, but what I do think would go a long way would be splitting the "Feature & Bug Voting" forum into "Feature Requests" and "Bug Reporting" forms.
Having users vote on Feature Requests makes a ton of sense... asking users to vote on bugs seems weird.
I also think this contributes to the impression that the Plex Team isn't focusing on squashing bugs but focusing on making new features.
This might be asking too much but if you took it a step farther and actively managed the Bug Reporting forms by marking threads about fixed bugs as [Solved] that would go pretty far in making people feel like the Plex Team is paying attention to users and focusing on fixing bugs.
At minimum spliting "Feature & Bug Voting" seems like a good idea.
Please don't make this public. The only thing it would do is to aggravate people who feel their pet bugs/features aren't getting the attention they think it deserves.
Multiple platform software development isn't easy and demanding more information, that isn't yours to demand in the first place, isn't going to magically make your issues go away. All it is going to do is give you more fuel to justify the way you feel.
Plex could show you the information they have in their internal planning/packaging tools but they can't control how you decide to interpret that information. Having an internal place to discuss features, bugs, their importance and priority means that developers and other Plex employees can be candid about those specific things.
It is intentionally ignorant to think that the Plex team is doing anything but working their ■■■■■ of on getting as many new features, bug fixes and dog pictures as they can.
Having paid paid for your Plex Pass doesn't mean you get to demand an ever increasing amount of things from the development team and Plex itself. It means that you paid for the features that were outlined https://plex.tv/subscription/welcomeon this page. They also went above and beyond that to create this forum section that allows you to have a voice in a discussion that might get more attention from the developers. It doesn't mean that you get to have a 1 on 1 discussion with Plex any time you decide that you want more than you have already.
Either the Plex Pass is worth it for you and you can continue paying it or it isn't and you can stop paying it.
Man you got it wrong on so many levels.
A well organized list of bugs view-able by customers is good. If you don't want to use it then you don't have. For those in the forums that help a lot of people it would come in handy as a source of reference and to be able to let other forum members know it's been acknowledged which many times we do not know at present.
No one is asking for their private list of things they are working on. Just a public list of issues US CUSTOMERS HAVE FOUND. These two lists could/can/will be quite different.
We all realize everyone is working hard on things. Don't think that is really an issue. But I'm sure many of the user bugs are either not on Plex's radar screen because they have been buried in the forums or they are old and no one has commented on them lately so it's as if they don't exist. A Public list of known issues will combat both of these problems.
This has nothing to do with Plex Pass. A bug is a bug regardless of free vs plex pass. If there is a known issue it should be reported.
If not a full public tracker it should at least be open to Plexpass members who are the ones actually getting new features first and might find issues that got past internal QA testing.
1. They don't have to make it writeable by users, can just make it readable (in case anyone is concerned about unwelcome/improper editing).
2. It's insanely frustrating for users to see certain bugs not addressed in years (ie: broken android sync). It feels like no one at the dev team cares, the public bug tracker can prove otherwise.
3. If users see the developer/milestone the bug is assigned to, they're more likely to help developer reproduce/debug the issue.
The likes didn’t carry over to the new forum, so please like it again.
Early 2021 clean-up: duplicate
