Repository navigation
[Child of #650] Audit: Issue Fields Configuration vs. GitHub API #660
Description
Overview
Validate that issue-fields.yml configuration is complete, correct, and aligns with GitHub's issue fields API.
Scope
- Review
.github/issue-fields.ymlconfiguration - 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.ymldocs/ISSUE-FIELDS.mddocs/ISSUE_TYPES.md
Related Documentation
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
Metadata
Metadata
Assignees
Type
Fields
Priority
None yet
Activity
linear-code commentedon May 31, 2026
LS-834
LS-1136
ashleyshaw commentedon Jun 3, 2026
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
fix: clear retired doc link validator findings (#807)
docs: align type:qa references with type:test mapping (#814)
ashleyshaw commentedon Jun 3, 2026
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.
fix(config): align issue type parity across canonical files (#788)
docs(audit): add Wave 5 Phase 1 audit deliverables (#790)
github-actions commentedon Jun 19, 2026
Missing required section(s): Definition of Ready (DoR), Definition of Done (DoD)
The issue will remain open and flagged until the body is corrected.
Please update the issue with one of the official templates:
If this was opened by automation, update the automation to preserve the template sections before creating the issue.
github-actions commentedon Sep 8, 2026
This issue has labels that are not in the canonical taxonomy:
migrate:priority:normalmigrate:type:auditarea:labelsValid Canonical Labels
Please use labels with a prefix from the canonical taxonomy:
type:bug,type:feature,type:task,type:documentation, etc.status:needs-triage,status:in-progress,status:done, etc.priority:critical,priority:high,priority:normal,priority:lowarea:ci,area:docs,area:labels,area:security, etc.meta:needs-changelog,meta:duplicate,meta:blocked, etc.For the complete list, see .github/labels.yml.