Skip to content
This repository has been archived by the owner on Nov 10, 2020. It is now read-only.

Github Labels

Jeff Keene edited this page Mar 27, 2018 · 9 revisions

This page is use to help explain how to use the labels in our github to assist in sprint planning.

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

enhancement:content

enhancement:tech

Ongoing Epic Story Labels

data

  • 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

Special Use Labels

blocked

  • Use this if the issue can not be worked on

help wanted

  • Use this issue to ???

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.
Clone this wiki locally