Skip to content

Labels

Labels

  • 0 - _Triaging

    New tickets that need to be hashed out a bit more before they hit the backlog.
  • 0 - Backlog

    Where tickets start after being triaged. This means the ticket has targeted milestone/labels.
  • 0 - Waiting on User

    Waiting on a response from either a commenter or ticket creator.
  • 1 - Ready

    Tickets that are on deck/assigned. All ready to go.
  • 2 - Working

    Tickets that are currently being worked on.
  • 3 - Review

    This is for tickets that need to be reviewed prior to being complete.
  • 4 - Done

    Tickets that have been completed and are ready for release.
  • 5 - Released

    The area addressed in the ticket has been released in the product and is generally available.
  • Blocked - External

    Issues that are blocked by something external to the code base.
  • BreakingChange

    A breaking change requires a major version bump (pre v1 does not apply in the same way).
  • Bug

    Tickets that represent defects/bugs.
  • BuildAutomation

    Issues and Tasks related to build automation.
  • ChocolateyForBusinessAzure

    Issue affects Chocolatey For Business in Azure Environment. Note the issue will be synced there.
  • Documentation

    This issue requires a change to documentation.
  • Duplicate Issue

    Issues that are duplicates.
  • Enhancement

    Enhancements are things that are improvements or features.
  • Hacktoberfest

    This issue is a giood issue to work on for Hacktoberfest.
  • hacktoberfest-accepted

    This issue / pull request has been accepted as part of Hacktoberfest.
  • invalid

    This is used to mark Hacktoberfest pull requests as invalid
  • Invalid / Not Issue / No repro / Not Implementing

    Tickets related to things that are invalid or are unable to be reproduced.
  • Multiple Environments

  • NO RELEASE NOTES

    Should not be included in the release notes - not enhancing or fixing end product.
  • No Response / Stale

    Issues that have had no updates and cannot be progressed.
  • Priority_HIGH

    Represents high priority tickets - things that must be addressed soon.
  • Priority_LOW

    Represents tickets that are of lower priority and can be taken care of whenever.
  • Security

    Related to security in some way. Much of what we do is centered around security and this is higher.
  • Task

    Non-bug, non-feature related things. Could be refactoring. Sometimes non-code related things.
  • Tests

    Issues related to the tests (NUnit or Pester)
  • Wrong Repository

    A ticket tied to the wrong repository would receive this label.