Skip to content

Label Definitions

Michael O'Connor edited this page Mar 24, 2021 · 6 revisions

Why we label

Color-coded labels help you categorize and filter your issues (just like labels in email). This allows for easier manipulation of tickets, lowering the amount of future time used to sort through them.

Label definitions:

*All issues on the Yumble project will have at least these 2 types of label.

  1. Environment label (labels that show what part of the codebase is affected by the issue)
  • These include:
    • Backend
    • Frontend
    • Documentation
  1. Timeline label (label that shows what part of the project (setup, initial list of tasks or implementation and wrap-up) Other than these labels there are a few to further distinguish functionality of the ticket.
  • These include:
    • Setup
    • Initial list of tasks
    • Implementation
    • Wrap up
  1. For any additional labels please make a feature request for it.
  • Approved labels include:
    • API discovery (all work towards API pulling)
    • API (all work towards Yumble API)
    • webSocket (all work towards Yumble webSocket)
    • Future work (work for the next group to improve / what we haven't finished in time)

Clone this wiki locally