Use GitHub Issue Types
Use organization issue types for a stable classification such as bug, feature or task, while labels express additional dimensions. A project single-select field is not the same metadata.
Step-by-step guide
Check access and scope
Organization owners manage available issue types. Confirm the repository belongs to the intended organization and its taxonomy is maintained.
Review organization types
Review the organization default types and definitions.
Adjust maintained definitions
Ask an owner to add or adjust a type only when necessary. Organization owners manage types from organization Settings > Planning > Issue types; repository labels remain a different classification mechanism.
- Worked example: An expired-link defect is a Bug, a configurable expiry capability is a Feature, and updating recovery instructions may be a Task. Priority and product area can remain separate labels.
Classify sample issues
Apply appropriate types to representative repository issues.
Filter by issue type
Use issue-type search or project filters for planning.
Review obsolete types
Review disabled or obsolete definitions before changing the taxonomy.
Verify the result
The issue displays its intended type and the corresponding project filter includes the sample.
Common mistakes
Check the handoff edge case
Adding near-duplicate types makes classification inconsistent. Define the distinction with examples before introducing a new type.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.