Problems, incorrect behavior or appearance

Refactoring, technological debt, etc.

The issue is a crash in the software

Issues that propose improvements to existing features

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.

New features or capabilities to be added

Mockups are available for this change or feature, but they need to be implemented still.

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.

Issue is an unintended break of previous working behavior

Security, privacy or safety issues

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)

Needs an acceptable design solution to be identified

The issue needs more diagnosis to triage

The issue needs more discussion before an action can be taken.

Needs additional information to be diagnosed and/or resolved

The task needs to be either closed or accepted

Request For Comments and discussions from developers

Issue describes something that does not need to be changed

Issue is too generic or is not actionable