[Child of #650] Audit: Issue Fields Configuration vs. GitHub API

[ashleyshaw]

Overview

Validate that issue-fields.yml configuration is complete, correct, and aligns with GitHub's issue fields API.

Scope

• Review .github/issue-fields.yml configuration
• Verify custom fields are properly defined
• Check field mappings to GitHub API
• Verify field values match what GitHub supports
• Test field creation/update via automation

Audit Checklist

• Extract all custom fields from issue-fields.yml
• Verify field naming conventions
• Check field types (single_select, date, text, etc.)
• Verify field values are valid GitHub options
• Check field descriptions are clear and complete
• Verify required field configurations
• Test field creation via API or workflow
• Identify any deprecated or unsupported fields

Deliverables

• Issue fields validation report
• Field configuration checklist
• Any identified GitHub API misalignments
• Test results and recommendations
• Documentation updates (if needed)

Related Files

• .github/issue-fields.yml
• docs/ISSUE-FIELDS.md
• docs/ISSUE_TYPES.md

Related Documentation

• Issue Fields Guide
• GitHub API - Issue Fields
• Canonical Issue Fields

---

Definition of Ready (DoR)

• Clear problem statement and expected outcome
• Acceptance criteria defined
• Related issues/dependencies identified
• Required resources/approvals listed

Definition of Done (DoD)

• All acceptance criteria met
• Changes tested and validated
• Documentation updated
• Changes merged and deployed
• Stakeholders notified

[linear-code]

LS-834

LS-1136

[ashleyshaw]

Phase 1 deliverable completed.\n\nDeliverable report:\n- https://github.com/lightspeedwp/.github/blob/develop/.github/reports/audits/2026-06-03-issue-fields-config-vs-github-api-audit-660.md\n\nPhase 2 follow-on parity implementation completed in config files:\n- https://github.com/lightspeedwp/.github/blob/develop/.github/issue-fields.yml\n- https://github.com/lightspeedwp/.github/blob/develop/.github/issue-types.yml\n- https://github.com/lightspeedwp/.github/blob/develop/.github/labels.yml\n\nValidation evidence:\n- scripts/validation/validate-issue-fields.cjs: pass\n- lint:yaml: pass\n- cross-file type parity: 0 mismatches

[ashleyshaw]

Status update (2026-06-03): Changes affecting this issue are now merged into develop via PR #814 (commit ea285b6). Current issue state remains as-is and reflects the delivered work.