https://github.com/imajes/plex-issue-tracking
Community-driven tracker for Plex Media Player bugs and feature feedback during public beta.
https://github.com/imajes/plex-issue-tracking
beta-testing bug-tracker community-feedback feature-requests issue-forms media-center open-source-support plex plex-media-player ux-feedback
Last synced: 4 months ago
JSON representation
Community-driven tracker for Plex Media Player bugs and feature feedback during public beta.
- Host: GitHub
- URL: https://github.com/imajes/plex-issue-tracking
- Owner: imajes
- Created: 2025-05-22T13:58:20.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2025-05-22T15:22:47.000Z (about 1 year ago)
- Last Synced: 2025-10-11T14:59:54.380Z (8 months ago)
- Topics: beta-testing, bug-tracker, community-feedback, feature-requests, issue-forms, media-center, open-source-support, plex, plex-media-player, ux-feedback
- Homepage:
- Size: 10.7 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 11
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# Plex Community Issue Tracker
Welcome! This is a **community-led issue tracker** designed to improve the quality, clarity, and visibility of bugs and feature requests for the Plex Media Player rebuild and public beta period.
We're a group of Plex users who believe feedback shouldn't get lost in a sea of forum threads and guesswork. While we are **not affiliated with the official Plex team**, our goal is to organize high-signal reports that can ultimately help the Plex team—and the wider user base.
---
## 🎯 Project Goals
- **Centralize** bug reports and feature suggestions for the Plex media player.
- **Filter noise** from community feedback by using structured GitHub issue forms.
- **Encourage adoption** by Plex through clean, consistent, and actionable user-submitted data.
- **Foster collaboration** among users via GitHub Issues, Discussions, and Projects.
- **Promote searchability** through structured input, consistent labels, and scoped Projects.
---
## 🛠 How to Contribute
### Report a Bug
Use the **Bug Report** form to document issues:
- What went wrong?
- On which platform?
- What were you doing?
- How can we reproduce it?
[➡️ Click here to file a bug](../../issues/new?template=bug_report.yml)
### 💡 Suggest a Feature
Use the **Feature Request** form to propose ideas that improve the experience:
- What problem are you solving?
- What’s your proposed solution?
- What platform(s) would benefit?
[➡️ Click here to request a feature](../../issues/new?template=feature_request.yml)
---
## 🧽 How We Organize Feedback
- **📂 Issues** — Our main intake method. Bugs and features are logged via structured forms. Using dropdowns and labels ensures that issues are easier to sort, group, and find later.
- **💬 Discussions** — Not a replacement for the Plex forums! These are for:
- Side conversations and exploration that fork off existing issues
- Reports that are incomplete or vague but worth follow-up
- Coordination among contributors on how to categorize or reframe an issue
- **📋 Projects** — Used like pivot tables: we track bugs or enhancements specific to platforms (e.g., Apple TV, Android) or specific Plex versions. This makes patterns and trends easier to surface.
- **🏷 Labels** — Automatically applied to sort by platform, frequency, severity, media type, and more. Helps streamline searching and filtering.
---
## 🙌 Why This Matters
We know reporting issues can feel thankless. Our hope is this tracker:
- Makes reporting easier
- Surfaces recurring problems faster
- Builds a bridge Plex might one day walk across
- Makes it easier for the community (and hopefully Plex) to **search, filter, and act** on what matters most
Whether you're here to fix, suggest, or just keep track: thanks for helping make Plex better for all of us.