[Wave 5.2.2] Reconcile Issue-Fields Type Mapping

[ashleyshaw]

Overview

Resolve the issue-fields.yml type field mapping to either expand to all 25 issue types or document why the current collapse to 4 generic values is intentional.

Context

Wave 5.2 audit identified that issue-fields.yml collapses 25 distinct issue types to 4 project field values:

• Epic → Task (loses nuance)
• Story → Task (loses nuance)
• Design → Task (loses nuance)
• All other types map to Bug, Feature, Documentation, or Task

Currently unmapped types: type:refactor, type:build

This causes loss of domain context in project views and makes work-type tracking impossible.

Acceptance Criteria

• Decision made: expand mapping or document collapse rationale
• All 25 issue types mapped (or documented as intentional collapse)
• issue-fields.yml updated with complete mapping
• Rationale documented in ISSUE_FIELDS.md
• Project field configuration verified

Technical Details

Options:

1. Expand mapping: Create 10+ project field values for type categories
2. Document collapse: Explain why 25 types intentionally map to 4 values

Recommend Option 1 for better project automation and tracking.

Effort Estimate

• 1-2 hours

Related

• Parent: [Audit] Canonical Config Files (labels, issue-types, issue-fields) #650 (Wave 5.2: Canonical Config Files Audit)
• Depends on: 5.2.1 (Color Strategy) — optional dependency
• Blocks: 5.2.4 (Documentation Updates)

---

Generated by Claude Code
https://claude.ai/code/session_01QBPjNAFgVUmE7RP658hut9"

[linear-code]

LS-849