Issue labels

Status labels

Closed

• duplicate
  • The issue is already being tracked.
  • These issues should always have a link to the original.
• outdated
  • The issue applies to a version that is no longer supported.
• wontfix
  • The issue does not need to be fixed.

Open (pending)

• needs-more-info
  • A maintainer needs more information to resolve an issue, such as reproducible steps for bugs, or clarification of a feature request.
  • If an issue with this label does not receive a reply within 7 days, the issue may be closed.
• postponed
  • The issue is waiting on another change or community feedback.

Severity labels

These labels are not applied to feature requests. Bugs and tasks that do not have a severity label are considered to be severity-normal by default.

If a maintainer decides that an issue does not block a release, its severity may be downgraded.

• severity-critical
  • The issue may cause corruption of stored data.
  • The issue may create a security vulnerability.
  • The issue may significantly affect deployment.
  • The issue may cause severe performance loss.
  • The issue may make multiple features unusable and does not have a workaround.
  • The issue cannot be resolved in a minor-level version update.
• severity-major
  • The issue may cause input to be lost, but does not corrupt stored data.
  • The issue may make a single feature unusable and does not have a workaround.
  • The issue is a significant developer experience regression.
  • The issue is a significant user experience regression.
  • The issue cannot be resolved in a patch-level version update.
• severity-normal
  • The issue has a workaround.
• severity-minor
  • The issue is cosmetic, such as an incorrect comment, typo, or bad formatting.

Community labels

These labels indicate that an issue has been triaged, approved for a later milestone, and may be resolved by a first-time contributor.

• difficulty-beginner
  • The issue will likely require minimal changes.
  • The issue should not disrupt other components.
• difficulty-intermediate
  • The issue will likely require many changes.
  • The issue should not disrupt other components.
• difficulty-advanced
  • The issue will likely require knowledge of multiple components.
  • The issue may require knowledge of code provided by a dependency.
  • The issue may require the use of other developer tool(s).