Labels

Indicates a PR that requires an org member to verify it is safe to test.

Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Higher priority than priority/awaiting-more-evidence.

Highest priority. Must be actively worked on as someone's top priority right now.

Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Denotes a PR that will be considered when it comes time to generate release notes.

Denotes a PR that introduces potentially breaking changes that require user action.

Denotes a PR that doesn't merit a release note.

Denotes a PR that changes 100-499 lines, ignoring generated files.

Denotes a PR that changes 30-99 lines, ignoring generated files.

Denotes a PR that changes 10-29 lines, ignoring generated files.

Denotes a PR that changes 500-999 lines, ignoring generated files.

Denotes a PR that changes 0-9 lines, ignoring generated files.

Denotes a PR that changes 1000+ lines, ignoring generated files.

Used during release burndown. Denotes an issue or PR is approved to be part of the release

Used during release burndown. Denotes that an issue is actively being worked.

Used during release burndown. Denotes that a fix for an issue is actively being reviewed.

To signal e2e test job to be run

Indicates an issue needs more information in order to work on it.

Indicates an issue can not be reproduced as described.

Indicates an issue that is a support question.

This will not be worked on