Issue Labels

We use a series of labels and bots to manage the backlog created on our repository. It's our aim to triage issues as quickly as possible while tracking reactions to feature and change requests made by you.

Types

1. feature request is for new functionality you want us to work on
2. change request is for existing functionality you want us to change
3. bug let's us know there is a problem you are experiencing
4. plan item is for specific work we are doing within a given month
5. iteration plan is for high level overviews of the work we are doing in a month

Service

A label to identify which specific App Center service an issue applies to will be added to all issues to better direct your request.

Examples: build, test, distribute, diagnostics, analytics, accounts, etc.

Triage

1. known issue is a third party dependency causing issues outside of our control
2. response required is used when we need some more information from you to keep the issue open
3. stale is used when an issue has not been modified in 90 days
4. keep is used to keep feature and change requests open that are building community interest

Automation

1. Issues marked response required by our team will be closed 7 days later if no response is received.
2. Issues will be marked stale after 90 days of inactivity and be automatically closed 7 days later.
3. Issues marked keep will not be automatically closed.