Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • Doing
    GNOME / chronojump
  • 1. Crash
    GNOME
    The issue is a crash in the software
  • 1. Bug
    GNOME
    Problems, incorrect behavior or appearance
  • Strategical
    GNOME / chronojump
    Some company involved with us is waiting this
  • 2. Needs Information
    GNOME
    Needs additional information to be diagnosed and/or resolved
  • EasyUseful
    GNOME / chronojump

    • Other labels

  • 9. openQA test failure in GNOME OS
    GNOME
    Issues which cause the openQA end-to-end tests of GNOME OS to fail in 'master'.
  • json
    GNOME / chronojump
  • Initiative: Update app metadata URLs
    GNOME
    Initiatives#51
  • 9. Initiative: Input hints
    GNOME
  • dotnet
    GNOME / chronojump
  • unicode
    GNOME / chronojump
  • arduino
    GNOME / chronojump
  • video
    GNOME / chronojump
  • Initiative: Low memory monitoring
    GNOME
    Initiatives#44
  • Initiative: Power-saver state
    GNOME
    Initiatives#43
  • Initiative: Metered data
    GNOME
    Initiatives#42
  • 1. Performance
    GNOME
    Human-perceptible delays in response time to user actions, or issues related to the excessive use of system resources like CPU, I/O, GPU, etc.
  • 2. Merge After Freeze
    GNOME
    This merge request has been accepted but should only be merged once the module emerges from code freeze (see https://wiki.gnome.org/ReleasePlanning/Freezes)
  • presentation
    GNOME / chronojump
  • version
    GNOME / chronojump
  • cloud
    GNOME / chronojump
  • OS:chromeos
    GNOME / chronojump
  • 0. Critical
    GNOME
  • 1. Cleanup
    GNOME
    Refactoring, technological debt, etc.
  • 1. Epic
    GNOME
    Initiatives and goals across modules and releases. Epics are scoped, prioritized (among other initiatives) and doable. Epics are adviced to follow a Minimum Viable Change approach.