This page explains how to use the labels in our github to assist in sprint planning.

When using the filter on Waffle, these labels can be used to view the related issues. We tried to define a faux hierarchy by using "text:subtext" format. By typing "bug:" into the filter search box you can see all the bug issues vs just seeing the "bug:visual" issues.

Core Labels:

Bug Labels: Use for fixing current tech

bug:visual

• Use this label for colors, alignment, font size, icons missing

bug:content

• Use this label for misspelling, wrong data being displayed, wrong labels

bug:tech

• Use this issue if there is a technical bug that needs to be addressed. For example a unit test issue.

Enhancement Labels: Use for enhancing the site/tech not to fix bugs.

enhancement:visual

• Use this label for colors, alignment, font size, icons. This is for a new feature.

enhancement:content

• Use this adding new data, articles

enhancement:tech

• Use this issue for usability improvements, refactoring or adding new tech improvements.

Ongoing Epic Story Labels

data-mgmt

• Use this label for adding and/or updating data on the site. Also can be used for data management tool work.

research

• Use this for tasks that are for research and Proof of Concepts

training

• Use this for providing training for the website

styleguide

• Use this for updating and maintaining our style guide

Special Use Labels

blocked

• Use this if the issue can not be worked on

help wanted

• Use this issue to flag for help from 18f

Priority Labels

p1

• Work on this immediately. Show stopper. Must Have for next release.

p2

• This is doesnt prevent the site from being used but needs to be addressed in the near term.

p3

• Not a show stopper and can be resolved at a later time

Custom Labels:

Use additional labels when we need have a new epic story to track. Please delete them when all stories have been completed.

• An example of this is the "Transition" label, used for tracking all the tasks 18f had to transition the work to ONRR.