Vorta Issue Triage Policy
Use this policy to classify, label, and manage GitHub issues for the Vorta project.
Core Principles
- Bugs should be found and addressed - prioritize by severity
- Feature requests adding complexity, dependencies, or affecting rare use cases - mark as
status:idea
- Issues already addressed - close with explanation
- Borg feature requests - mark as
status:wontfix with comment directing to BorgBackup
- Issues needing testing on specific systems - mark as
help wanted
- Support requests - try to respond if issue is less than 60 days old. Close support requests after 90 days. Mark
type:support.
Available Labels
Type Labels
type:bug - Something doesn't work as intended
type:enhancement - Improvement of an existing function
type:feature - New functionality
type:question / type:support - Questions about using Vorta
type:docs - Documentation issues
type:refactor - Code refactoring
type:translations - Translation problems
Priority Labels
priority:high - Security issues, data loss risks, crashes in core functionality
priority:medium - Broken features with workarounds
priority:low - Cosmetic issues, minor improvements, edge cases
Status Labels
| Label |
When to Apply |
status:idea |
Valid suggestion but: adds complexity, requires external dependencies, environment-specific, or rare use case. Keep open for discussion. |
status:wontfix |
Outside project scope OR belongs in Borg itself. Close with explanation. |
status:duplicate |
Already reported. Close and link to original. |
status:invalid |
Not actionable or not a Vorta issue. Close. |
status:needs details |
Missing reproduction steps, version info, or logs. |
status:not-reproducible |
Cannot reproduce with provided information. |
status:planning |
Large accepted feature needing design discussion. |
status:ready |
Fully specified, ready for implementation. |
status:stale |
No activity for 60+ days awaiting reporter response. |
Platform Labels
os:linux, os:macos, os:windows
package:flatpak, package:pip, package:native-linux, package:pyinstaller
Contributor Labels
help wanted - Maintainers need community help (testing, implementation)
good first issue - Simple change for new contributors
Decision Tree for Feature Requests
Is this a Borg feature request?
├─ YES → status:wontfix, close with comment linking to BorgBackup issues
└─ NO → Continue...
Does it add significant complexity?
├─ YES → status:idea
└─ NO → Continue...
Does it require new external dependencies?
├─ YES → status:idea
└─ NO → Continue...
Does it only work in specific environments?
├─ YES → status:idea (+ help wanted if testing needed)
└─ NO → Continue...
Is it a rare/niche use case?
├─ YES → status:idea
└─ NO → Accept as type:feature or type:enhancement
When to Close Issues
Close immediately with explanation:
- Fixed in current version (reference PR/commit)
- Duplicate (link to original issue)
- Belongs in Borg, not Vorta (
status:wontfix)
- Outside project scope (
status:wontfix)
- Invalid or spam (
status:invalid)
Close after waiting period:
- No response to
status:needs details for 30+ days → add status:stale, close after 14 more days
- Cannot reproduce and reporter unresponsive
Keep open with status:idea:
- Valid suggestion that doesn't fit current priorities
- Community may contribute implementation
- May become relevant in future
Required Information for Bug Reports
Before marking as status:needs details, check for:
- Vorta version
- OS and version
- Borg version
- Steps to reproduce
- Expected vs actual behavior
- Relevant logs (Help → Debug Log)
Comment Templates
For Borg Feature Requests
This feature would need to be implemented in BorgBackup itself rather than Vorta.
Vorta is a GUI wrapper and relies on Borg's capabilities.
Please consider opening a feature request at: https://github.com/borgbackup/borg/issues
Closing as `wontfix` since this is outside Vorta's scope.
For Ideas (complexity/dependencies)
Thank you for this suggestion! This is an interesting idea, but it would add
significant complexity / require external dependencies / only affect specific
environments.
Marking as `idea` to keep the discussion open. Community contributions are welcome
if someone wants to implement this.
For Already Fixed Issues
This has been addressed in version X.Y.Z / commit abc123 / PR #NNN.
[Brief explanation of how it was fixed]
Closing as resolved.
For Needs Testing
We cannot reproduce/test this on [platform]. Adding `help wanted` - if you have
access to [specific environment], please help verify this issue.
Label Combinations Quick Reference
| Scenario |
Labels |
| Critical bug |
type:bug, priority:high |
| Minor Linux-only bug |
type:bug, priority:low, os:linux |
| Good starter task |
help wanted, good first issue |
| Needs macOS testing |
help wanted, os:macos |
| Complex feature request |
status:idea, type:feature |
| Flatpak packaging issue |
type:bug, package:flatpak |
| Borg feature request |
status:wontfix (then close) |
| Accepted large feature |
status:planning, type:feature |
Periodic Maintenance
- Monthly: Review
status:needs details issues, apply status:stale if no response
- Quarterly: Review
status:idea issues for relevance, close if obsolete
- Per release: Close issues fixed in release, update milestones
- System health check: Run
python scripts/triage_utils.py to verify dependency integrity and system state
1---2name: issue-triage-53description: Triage and classify GitHub issues for the Vorta project. Use when reviewing issues, applying labels, deciding whether to close issues, or evaluating feature requests against project scope.4user-invocable: true5metadata:6 source: https://skillmd.com/skills/bishal-pdmsft/issue-triage-57---89# Vorta Issue Triage Policy1011Use this policy to classify, label, and manage GitHub issues for the Vorta project.1213## Core Principles14151. **Bugs should be found and addressed** - prioritize by severity162. **Feature requests adding complexity, dependencies, or affecting rare use cases** - mark as `status:idea`173. **Issues already addressed** - close with explanation184. **Borg feature requests** - mark as `status:wontfix` with comment directing to BorgBackup195. **Issues needing testing on specific systems** - mark as `help wanted`206. **Support requests** - try to respond if issue is less than 60 days old. Close support requests after 90 days. Mark `type:support`.2122## Available Labels2324### Type Labels25- `type:bug` - Something doesn't work as intended26- `type:enhancement` - Improvement of an existing function27- `type:feature` - New functionality28- `type:question` / `type:support` - Questions about using Vorta29- `type:docs` - Documentation issues30- `type:refactor` - Code refactoring31- `type:translations` - Translation problems3233### Priority Labels34- `priority:high` - Security issues, data loss risks, crashes in core functionality35- `priority:medium` - Broken features with workarounds36- `priority:low` - Cosmetic issues, minor improvements, edge cases3738### Status Labels39| Label | When to Apply |40|-------|---------------|41| `status:idea` | Valid suggestion but: adds complexity, requires external dependencies, environment-specific, or rare use case. Keep open for discussion. |42| `status:wontfix` | Outside project scope OR belongs in Borg itself. Close with explanation. |43| `status:duplicate` | Already reported. Close and link to original. |44| `status:invalid` | Not actionable or not a Vorta issue. Close. |45| `status:needs details` | Missing reproduction steps, version info, or logs. |46| `status:not-reproducible` | Cannot reproduce with provided information. |47| `status:planning` | Large accepted feature needing design discussion. |48| `status:ready` | Fully specified, ready for implementation. |49| `status:stale` | No activity for 60+ days awaiting reporter response. |5051### Platform Labels52- `os:linux`, `os:macos`, `os:windows`53- `package:flatpak`, `package:pip`, `package:native-linux`, `package:pyinstaller`5455### Contributor Labels56- `help wanted` - Maintainers need community help (testing, implementation)57- `good first issue` - Simple change for new contributors5859## Decision Tree for Feature Requests6061```62Is this a Borg feature request?63├─ YES → status:wontfix, close with comment linking to BorgBackup issues64└─ NO → Continue...6566Does it add significant complexity?67├─ YES → status:idea68└─ NO → Continue...6970Does it require new external dependencies?71├─ YES → status:idea72└─ NO → Continue...7374Does it only work in specific environments?75├─ YES → status:idea (+ help wanted if testing needed)76└─ NO → Continue...7778Is it a rare/niche use case?79├─ YES → status:idea80└─ NO → Accept as type:feature or type:enhancement81```8283## When to Close Issues8485**Close immediately with explanation:**86- Fixed in current version (reference PR/commit)87- Duplicate (link to original issue)88- Belongs in Borg, not Vorta (`status:wontfix`)89- Outside project scope (`status:wontfix`)90- Invalid or spam (`status:invalid`)9192**Close after waiting period:**93- No response to `status:needs details` for 30+ days → add `status:stale`, close after 14 more days94- Cannot reproduce and reporter unresponsive9596**Keep open with `status:idea`:**97- Valid suggestion that doesn't fit current priorities98- Community may contribute implementation99- May become relevant in future100101## Required Information for Bug Reports102103Before marking as `status:needs details`, check for:104- Vorta version105- OS and version106- Borg version107- Steps to reproduce108- Expected vs actual behavior109- Relevant logs (Help → Debug Log)110111## Comment Templates112113### For Borg Feature Requests114```115This feature would need to be implemented in BorgBackup itself rather than Vorta.116Vorta is a GUI wrapper and relies on Borg's capabilities.117118Please consider opening a feature request at: https://github.com/borgbackup/borg/issues119120Closing as `wontfix` since this is outside Vorta's scope.121```122123### For Ideas (complexity/dependencies)124```125Thank you for this suggestion! This is an interesting idea, but it would add126significant complexity / require external dependencies / only affect specific127environments.128129Marking as `idea` to keep the discussion open. Community contributions are welcome130if someone wants to implement this.131```132133### For Already Fixed Issues134```135This has been addressed in version X.Y.Z / commit abc123 / PR #NNN.136137[Brief explanation of how it was fixed]138139Closing as resolved.140```141142### For Needs Testing143```144We cannot reproduce/test this on [platform]. Adding `help wanted` - if you have145access to [specific environment], please help verify this issue.146```147148## Label Combinations Quick Reference149150| Scenario | Labels |151|----------|--------|152| Critical bug | `type:bug`, `priority:high` |153| Minor Linux-only bug | `type:bug`, `priority:low`, `os:linux` |154| Good starter task | `help wanted`, `good first issue` |155| Needs macOS testing | `help wanted`, `os:macos` |156| Complex feature request | `status:idea`, `type:feature` |157| Flatpak packaging issue | `type:bug`, `package:flatpak` |158| Borg feature request | `status:wontfix` (then close) |159| Accepted large feature | `status:planning`, `type:feature` |160161## Periodic Maintenance162163- **Monthly**: Review `status:needs details` issues, apply `status:stale` if no response164- **Quarterly**: Review `status:idea` issues for relevance, close if obsolete165- **Per release**: Close issues fixed in release, update milestones166- **System health check**: Run `python scripts/triage_utils.py` to verify dependency integrity and system state