-
Notifications
You must be signed in to change notification settings - Fork 3
Label Style Guide
In order to improve organization and tracking of issues, the following labels should be used as described.
Section of Reparo that this issue belongs to.
api
website
cli
Issues that make Reparo feel broken or prevent us from doing further work. High priority, especially if present in production.
blocked
blocker
bug
externally blocked
hotfix
Issues that affect a user's comprehension or overall enjoyment of the product.
visual design
copy
user experience
developer experience
Environment that the issue is present in.
local
production
Issues that are necessary but less impactful for our users.
cleanup
technical debt
experience debt
refactor
Issues that require further conversation to figure out how to proceed or what action steps are needed.
request for comments
help wanted
question
research
strategy
ready for review
stub
prototype
Issues that will result in new functionality or releases.
feature
Issues that will iterate on existing functionality.
enhancement
optimization
Issues where action can be taken, but has not yet.
under consideration
Issues where no actions are needed or possible. The issue is either fixed, addressed better by other issues
invalid
won't fix
duplicate
on hold
Epics track multiple stories together towards a desired outcome. Each epic should get a label unique to the core concept of the epic, usually 2-3 words. Epics should be labeled with their epic label and the epic
label. Each story related to an epic should be labeled with that epic's label.
epic