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.
apiwebsitecli
Issues that make Reparo feel broken or prevent us from doing further work. High priority, especially if present in production.
blockedblockerbugexternally blockedhotfix
Issues that affect a user's comprehension or overall enjoyment of the product.
visual designcopyuser experiencedeveloper experience
Environment that the issue is present in.
localproduction
Issues that are necessary but less impactful for our users.
cleanuptechnical debtexperience debtrefactor
Issues that require further conversation to figure out how to proceed or what action steps are needed.
request for commentshelp wantedquestionresearchstrategyready for reviewstubprototype
Issues that will result in new functionality or releases.
feature
Issues that will iterate on existing functionality.
enhancementoptimization
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
invalidwon't fixduplicateon 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