Prioritized Labels
  • critical
    Tickets that are emergency and need to be dealt with immediately (as in "drop everything, everyone work on this issue")
    • Project label
  • high
    High priority are things that are very important. Do them before other tickets, but generally follow normal workflow.
    • Project label
  • medium
    This is the default priority. You should use this priority, unless you have very good reasons to do otherwise. Those tickets should be completed before the milestone is considered done.
    • Project label
  • low
    These are tickets that are useful, but we may or may not have time to do them. We can release the code if those are not done.
    • Project label
  • Other Labels
  • unittests needed
    • Project label
  • tests
    • Project label
  • subnet_cmds
    • Project label
  • stork
    Features and tickets related to Stork
    • Project label
  • stats
    Anything related to libstats or statistics in general.
    • Project label
  • sphinx
    • Project label
  • security
    • Project label
  • scripts
    • Project label
  • removal-candidate
    Issues that are candidates for removal. Label used sporadically, during around milestone ends/beginnings.
    • Project label
  • reconfigure
    Anything related to IPv6 reconfigure mechanism
    • Project label
  • rbac-tls
    Role-Based-Access-Control and TLS support
    • Project label
  • raspberry
    Stuff related to Raspberry Pi and cross-compilation
    • Project label
  • radius
    • Project label
  • qa needed
    Tasks and MRs in this state are should be evaluated or otherwise require some actions by QA.
    • Project label
  • qa
    QA-related task, e.g. testing, developing code needed for testing
    • Project label
  • premium
    • Project label
  • pgsql
    Anything PostgreSQL related
    • Project label
  • performance
    • Project label
  • perfdhcp
    • Project label
  • patch
    • Project label