Skip to content

Labels we're using in repos

Jump to bottom
Arti Walker-Peddakotla edited this page Dec 16, 2016 · 3 revisions

Current Problem:

We've got a lot of work going in different repos. And currently, we use a different set of labels for each repo. In order to streamline and codify the labels used to tag issues, we're going to move towards group labels based on broad themes, and try and keep labels consistent across repositories.

Doing this will ensure that:

  1. The priority label in one repo means the same thing as the priority label in another
  2. Create a consistent, easily translatable way for the team to tag their issues.
  3. Allow for easier switching between projects, since the vocabulary will be similar between the repos within our Github organization.
  4. Allow for ease of organization and prioritization of the issues in the product backlog.

These are the high level themes that I'd like to group labels by, and the respective labels that will be used in each theme. Each theme will have its own color scheme, so that we can easily identify if something is a platform issue, bug, etc.

Theme Color Description Labels
Platform #c7def8 The browser/mobile device/etc Firefox, IE, Mobile Safari, Safari, Chrome, Mobile Chrome
Problems #e11d21 Issues w/ product bug, security
Experience #d4c5f9 Affect's user's comprehension/enjoyment/experience w/ product copy, ux, ui, accessibility
Additions #bfdadc New ideas, new functionality feature request, user requested
Improvements #5319e7 Iterations on existing features enhancement, optimization
Priority #eb6420 Levels defining the timeline that bugs should be fixed in. Only used for bugs P1, P2, P3, P4, P5
??? #0e8a16 What mechanism is being used to annotate? (needs improvement) Chrome Ext, FF Ext, via

This idea was inspired (and copied from) this post: https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues/

Clone this wiki locally