FiftyOne Issue Triage
Categories
| Category |
When to Use |
| Already Fixed |
Resolved in recent commits/releases |
| Won't Fix |
By design, out of scope, or external behavior (browser, OS, third-party) |
| Not Reproducible |
Cannot reproduce with provided info |
| No Longer Relevant |
Outdated version, deprecated feature, or stale (6+ months) |
| Still Valid |
Confirmed bug or valid feature request needing work |
Workflow
1. Fetch Issue
gh issue view {number} --repo voxel51/fiftyone --json title,body,author,state,labels,comments
2. Analyze
- Extract: issue type, version, reproduction steps, error message
- Search related:
gh issue list --repo voxel51/fiftyone --state all --search "keyword"
- Check git history:
git log --oneline --grep="keyword"
3. Assess Responsibility
- External behavior (browser, OS, third-party)? → Won't Fix
- User workflow/configuration issue? → Won't Fix (with workaround)
- FiftyOne code/behavior issue? → Continue assessment
4. Assess Value
Before proposing fixes, ask: "Is a fix worth the effort?"
- How many users affected?
- Is workaround simple?
- Would fix add complexity or hurt performance?
5. Check Documentation
grep -r "keyword" docs/source/ --include="*.rst"
6. Categorize and Respond
Quick Reference
| Category |
Key Indicator |
Action |
| Already Fixed |
Found in git log |
Point to PR, suggest upgrade |
| Won't Fix |
External/by design |
Explain, provide workaround |
| Not Reproducible |
Can't reproduce |
Request more info |
| No Longer Relevant |
Old/stale/deprecated |
Explain, suggest new issue |
| Still Valid |
Confirmed, no fix |
Document root cause, propose fix |
Response Tone
Always start with thanks, be friendly, then explain. Keep responses simple (no internal code details).
If User Willing to Contribute
1---2name: fiftyone-issue-triage3description: Triages FiftyOne GitHub issues by categorizing as fixed, won't fix, not reproducible, or still valid. Use when reviewing GitHub issues, triaging bugs, or closing stale issues in the voxel51/fiftyone repository.4---56# FiftyOne Issue Triage78## Categories910| Category | When to Use |11|----------|-------------|12| **Already Fixed** | Resolved in recent commits/releases |13| **Won't Fix** | By design, out of scope, or external behavior (browser, OS, third-party) |14| **Not Reproducible** | Cannot reproduce with provided info |15| **No Longer Relevant** | Outdated version, deprecated feature, or stale (6+ months) |16| **Still Valid** | Confirmed bug or valid feature request needing work |1718## Workflow1920### 1. Fetch Issue21```bash22gh issue view {number} --repo voxel51/fiftyone --json title,body,author,state,labels,comments23```2425### 2. Analyze26- Extract: issue type, version, reproduction steps, error message27- Search related: `gh issue list --repo voxel51/fiftyone --state all --search "keyword"`28- Check git history: `git log --oneline --grep="keyword"`2930### 3. Assess Responsibility31- External behavior (browser, OS, third-party)? → Won't Fix32- User workflow/configuration issue? → Won't Fix (with workaround)33- FiftyOne code/behavior issue? → Continue assessment3435### 4. Assess Value36Before proposing fixes, ask: "Is a fix worth the effort?"37- How many users affected?38- Is workaround simple?39- Would fix add complexity or hurt performance?4041### 5. Check Documentation42```bash43grep -r "keyword" docs/source/ --include="*.rst"44```4546### 6. Categorize and Respond4748## Quick Reference4950| Category | Key Indicator | Action |51|----------|---------------|--------|52| Already Fixed | Found in git log | Point to PR, suggest upgrade |53| Won't Fix | External/by design | Explain, provide workaround |54| Not Reproducible | Can't reproduce | Request more info |55| No Longer Relevant | Old/stale/deprecated | Explain, suggest new issue |56| Still Valid | Confirmed, no fix | Document root cause, propose fix |5758## Response Tone5960Always start with thanks, be friendly, then explain. Keep responses simple (no internal code details).6162## If User Willing to Contribute6364- **Contribution guide:** https://docs.voxel51.com/contribute/index.html65- **Discord:** https://discord.com/invite/fiftyone-community (#github-contribution channel)66- Point to relevant code files for the fix
AdonaiVera