Labels

• bug

  Unwanted or unintended property causing functional harm
• chore

  Necessary but less impactful tasks such as cleanup or reorg
• copy

  Related to customer visible copy (messages, labels, etc)
• dependencies

  Pull requests that update a dependency file
• design

  Approach visual or engineering to apply to a product, API, or other effort.
• discussion

  Under consideration and/or debate.
• duplicate

  Issue exists. Add reference to pre-existing issue and close.
• enhancement

  Iterations on existing features or infrastructure.
• Epic

  Contain issues related by subject. Epics can span multiple repositories and multiple milestones.
• feature

  Brand new functionality. New pages, workflows, endpoints, etc.
• good first issue

  Appropriate for a new open source contribution.
• help wanted

  Open source contributions actively sought.
• Impacts DOCS

  Requires new or updates to our documentation.
• in-progress

  Taking action, but need a few things to happen first.
• invalid

  Does not apply to product, wrong repo. Close after applying this label.
• legal

  Concerned with rights, licensing, or a law
• on hold

  No action possible but still being considered.
• optimization

  Update speed, efficiency, or quality of a feature.
• P1 Bug

  Priority 1 Critical functionality not working Impacts all/most customers
• P2 Bug

  Priority 2 Critical functionality not working Impacts one/few customers
• P3 Bug

  Priority 3 There are workarounds, or the functionality is secondary
• P4 Bug

  Priority 4 Edge cases, improvements, items to be refactored soon
• production

  Present in or related to a production environment.
• qa
• question

  Inquiry inviting a reply. Point of controversy.
• released
• request-for-comment

  Requires further input to figure out tasks. Add to external requests.
• security

  Problem that potentially risks product, data, or other security.
• staging

  Present in or required by staging environment
• test

  Present or required by test environment