issuetype

IssueType is a metadata field used in issue tracking systems to classify an issue by the nature of the work it represents. It helps teams distinguish between different kinds of work and supports triage, assignment, reporting, and workflow routing.

Common values for issueType include bug, task, feature, improvement, epic, story, defect, incident, support, change request, and documentation. The exact set of types varies by tool and project, and in many systems the types can be customized or extended. Some tools also support subtypes or hierarchical arrangements, where a sub-task inherits characteristics from its parent type.

Purpose and usage: issueType guides how issues are handled throughout their lifecycle. It informs which team or developer is responsible, influences which workflows or transitions are available, and enables targeted reporting and dashboards. Consistent use of issue types improves metrics such as throughput, cycle time, and backlogs, and supports automation rules that act on specific types.

Structure and customization: In many systems, issueType is defined as a separate type entity, with attributes like description, category (defect vs work item), and whether it is a sub-task. Projects or organizations can often configure their own schemes to map issue types to workflows, permissions, and SLA rules.

Relation to tools: Some platforms emphasize issue types as core concepts (for example, Jira and YouTrack), while others rely more on labels or tags to classify work.

Best practices: maintain a concise, stable set of types; document guidelines for when to use each type; avoid duplicating meanings; regularly review type usage and adjust configurations to support reporting and automation.