Label Definitions

Labels can be applied to issues and pull requests to signify priority, category, or any other information that you find useful. Using labels all pull requests or issues could easily be filtered and tracked. The UI for UWP repository provides the following labels:

Area labels

• area: build & ci - indicates the pull request/issue is connected to the CI build of the repository.
• area: chart - indicates the pull request/issue is connected to the Chart control.
• area: datacontrols - indicates the pull request/issue is connected to the controls that are part of the DataControls project.
• area: dataviz - indicates the pull request/issue is connected to the controls that are part of the DataVisualization project.
• area: grid - indicates the pull request/issue is connected to the DataGrid control.
• area: input - indicates the pull request/issue is connected to the controls that are part of the Input project.
• area: map - indicates the pull request/issue is connected the Map control.
• area: primitives- indicates the pull request/issue is connected to the controls that are part of the Primitives project.

Type

• bug - the logged issue or created pull request is connected with a bug in the controls.
• feature request - the logged issue or created pull request is connected with a feature (added new functionality) in the controls.
• question - the logged issue is considered as a question about the controls.
• breaking change - this label is used to indicate that the logged issue used to be working before and some new functionality or fix has introduced it.
• invalid - the logged issue or pull request is considered to be invalid (issues or requests marked with invalid are mostly closed).

Effort

The issue or pull request marked with that label indicates the time that is needed the issue to be closed.

• effort: easy (hours) - the issue is consider as easy and could be resolved for hours. No core functionality is affected.
• effort: hard (weeks) - the issue is consider as hard and could be resolved for several weeks. A changes in core functionality is required.
• effort: medium (days) - the issue is consider as medium and could be resolved for several days.

Severity

• severity: critical - indicates that the issue makes the control unusable.
• severity: high - indicates that the issue breaks core feature.
• severity: low - very hard to reproduce issue that doesn't break core functionality.
• severity: medium - indicates that a functionality/feature of the control does work, but the issue is not easy to be reproduced.

Status

• status: InProgress - indicates that somebody is working on resolving the issue.
• status: Ready for test - the issue has been resolved and needs to be tested.
• status: Done - the issue has been resolved and has been tested.
• status: wontfix - the issue won't be fixed. An additional information should be provided why the issue won't be resolved. Issues marked with that label are closed.

Other

• CLA: NO - the user that has created a pull request connected with a specific issue hasn't signed the Contributor License Agreement.
• CLA: YES - the user that has created a pull request connected with a specific issue has signed the Contributor License Agreement
• need more info - additional information is needed in order to be able to reproduce the issue.