We group labels by color. This will help to clarify what kind of issue it is. We have determined the following groups and labels.
Issues that make the product feel broken. High priority, especially if its present in production.
Converting measurements, reorganizing folder structure, writing documentation, and other necessary (but less impactful) tasks.
Affect user’s comprehension, or overall enjoyment of the product. These can be both opportunities and “UX bugs”.
Server environment. In which environment did you find the bug. With good QA, you’ll identify issues on test and staging deployments.
Requires further conversation to figure out the action steps. Most feature ideas start here.
Iterations on existing features or infrastructure. Generally these update speed, or improve the quality of results. Adding a new “Prop” field to an existing Component in the API, for example.
Brand new functionality. New Component, workflows, etc.
Taking action, but need a few things to happen first. A feature that needs dependencies merged, or a bug that needs further data.
No action needed or possible. The issue is either fixed, addressed better by other issues, or just out of product scope.
Action taken but got stuck on something. Another contributor will be able to see that help is wanted.
Kind of type this PR should be released in. Patch, minor or major according to semver. Labels meant for PR's
| Group | ----------- | ------------------- | ------------- | ----------------- |
|---|---|---|---|---|
| Problems | bugs | security | ||
| Mindless | chore | refactor | documentation | |
| Experience | design | ux | affordance | styling |
| Environment | production | staging | test | |
| Feedback | question | request for comment | discussion | |
| Improvements | enhancement | optimization | ||
| Additions | feature | |||
| Pending | in progress | watchlist | ||
| Inactive | wont fix | on hold | invalid | duplicate |
| Help Wanted | help wanted | |||
| Release | major | minor | patch | ready for release |