Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • Blocked
    Oak-Tree
    It's not possible to pursue development of the issue because of problems. Issues that are permanently blocked should be tagged with "Dead."
  • Dead
    Oak-Tree
    A permanently blocked issue. It might come back to life, but ... it's not likely.
  • Discovery
    Oak-Tree
    Issues which are currently in a state of planning and preparation, where requirements are being discussed and specifications being written.
  • Sprint: Planning
    Oak-Tree
    Issues that are currently in the planning stage
  • Sprint: Future
    Oak-Tree
    Issues that will be tackled at some future point (probably in a month)
  • Duplicate
    Oak-Tree
    Issue is a duplicate of another issue and adds nothing (or very little) that is new
  • !!!! Blocking
    Oak-Tree
    Fix it!!! Highest priority issues which are preventing other work from being done.
  • This is important, do it now!
  • !! Moderate
    Oak-Tree
    Issue which should be moved into development using a normal process.
  • ! Low
    Oak-Tree
    Low priority development item. Represents a nice to have which we might get too (eventually).
  • Specification
    Oak-Tree
    Describe how something should be done so that when you start, you don't make a mess
  • In-Development
    Oak-Tree
    Currently being worked on, expect updates soon ...
  • Testing
    Oak-Tree
    The issue has been implemented, prepared, and packaged. It is currently waiting on the results of testing (unit, integration, functional, or production) before being closed. Basically, really almost done (for real).
  • Sprint: Current
    Oak-Tree
    Issues that are queued to be worked on now (but are not currently in development)
  • Operations
    Oak-Tree
    Involves the operations of the technology. Might be related to platform, configuration, or runtime environment.
  • Documentation
    Oak-Tree
    Examples, architectural explanations, and reference. Stuff needed to effectively use the software that has been created.
  • Prototype
    Oak-Tree
    The first time you attempt to do something, you'll get it wrong, so build a prototype first. (Another way of saying we might not know how to do this.)
  • Automation
    Oak-Tree
    This task should be performed by a machine in a repeatable and robust manner.
  • Task requires frontend JavaScript and React development skills
  • Review (Staging)
    Oak-Tree
    The issue is currently in staging and requires review, or has appeared as part of quality assurance and needs to be addressed.