This repository has been archived by the owner on Nov 10, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 40
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.
- Use this label for colors, alignment, font size, icons missing
- Use this label for misspelling, wrong data being displayed, wrong labels
- Use this issue if there is a technical bug that needs to be addressed. For example a unit test issue.
- Use this label for adding and/or updating data on the site. Also can be used for data management tool work.
- Use this for tasks that are for research and Proof of Concepts
- Use this for providing training for the website
- Use this if the issue can not be worked on
- Use this issue to ???
- Work on this immediately. Show stopper. Must Have for next release.
- This is doesnt prevent the site from being used but needs to be addressed in the near term.
- 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.
- Problem statement
- Product vision
- User scenarios
- What we're not trying to do
- Product risks
- Prioritization scale
- Joining the team
- Onboarding checklist
- Working as a distributed team
- Planning and organizing our work
- Sample retro doc
- Content style guide
- Content editing and publishing workflow
- Publishing a blog post
- Content audits: a (sort-of) guide
- User centered design process
- Research norms and processes
- Usability testing process
- Observing user research
- Design and research in the federal government
- Shaping process
- Preview URLs
- How to prepare and review PRs
- Continuous integration tools
- Releasing changes
- Github Labels