There are a few pre-defined label families to organize/search issues.
type
: issue typetype:bug
is attached to bug reportstype:enhancement
is attached to enhancement requests or suggestionstype:test
is attached to test improvements or failure reportstype:task
is attached to general taskstype:documentation
is attached to tasks relate to documentationfix-version
: the versions in which a bug or enhancement is planned to be releasedfix-version:10.0.0
affects-version
: the versions in which a bug was foundtype:bug
affects-version:9.1.0
module
: Lucene modulemodule:core/index
, module:analysis
tool
: toolingtool:build
, tool:release-wizard
A type
label is automatically attached to an issue by the issue template that the reporter selected. Other labels such as fix-version
may be manually added by committers.
If necessary, uncategorized labels may also be used.
good first issue
discuss
duplicate
website
Committers can add/edit labels manually or programmatically using Labels API.
Each issue template (web form) is associated with one type
label. You should add an issue template when adding a new type
label and vice versa.
Bug Report
is associated with type:bug
labelEnhancement Request/Suggestion
is associated with type:enhancement
labelTest Improvement / Failure Report
is associated with type:test
labelTask
is associated with type:task
labelDocumentation
is associated with type:documentation
labelIssue templates are written in YAML format and committed in .github/ISSUE_TEMPLATE
. See GitHub documentation for details.