It be nice to know what bugs are known and how long they’ve been open, even if we don’t have access to the code or assignment status. If nothing else it would help prevent people from opening the same “topic” over and over in the forums. Nothing is more frustrating than finding your exact problem with no response from Plex. It looks very unprofessional when you having your customers asking the same question with no answer, over and over again. Even worse when you have ChatGPT scraping your forums and providing “answers” based off the guesses and brainstorming around the problems on the forums.
My guess is that they are using GitHub with private repositories and so probably also using GitHub’s tracker internally. Unfortunately, you cannot have private repos with public issue tracking. The “solution” is to create an empty repo that only is use for issue tracking. I wonder if we can convince Plex to create a new repo for public issue tracking and then duplicate issues between their “internal” and “external” trackers… There actually is this and this project that might work for the sync process too.
If they won’t do that, the least they could do is make a new high-level category here in the forums called “Known Issues” that we could use for reporting and tracking.
