A mechanism for grouping/tagging issues. E.g. “Good First Issue”, “Documentation”, “Technical Debt”. Issue categories can be organized into a hierarchy, e.g. “Technology/Java/Cloud/Spring”.

Issue category may be assigned weight which can be used for balanced allocation of efforts into “buckets”. E.g. “Technical Debt” category may have weight 0.1, which would mean that 10% of each increment shall be spent on addressing technical debt (if there are issues in that category).

Issue category may also be marked as “cumulative”, which means that unspent capacity carries over. E.g. if a team spent 8% of their capacity on addressing technical debt in June, then they are expected to spend 12% in July.

Supertypes

Referrers

If true, unused category weight “capacity” is carried over to future increments and overused is subtracted from future increments. This allow low-weight categories to accumulate weight over time.

Type EBoolean
Cardinality 0..1
Changeable true
Derived false

Category relative importance. Can be used to allocate issues to increments in a balanced way.

Type EDouble
Cardinality 0..1
Changeable true
Derived false

Allocations for this category.

Type Allocation
Cardinality 0..*
Changeable false
Derived true
Opposite category

Issue categories can form a hierarchy.

Type IssueCategory
Cardinality 0..*
Changeable true
Derived false
Key path

Issues in the category.

Type Issue
Cardinality 0..*
Changeable false
Derived true
Opposite categories