Configure GitHub Project Custom Fields
Add project fields for planning decisions that are not already represented by repository metadata. Keep their meaning distinct from labels, issue types and issue state.
Step-by-step guide
Check access and scope
You need write permission to the project. Decide which fields are project-local and which metadata should be maintained on the underlying issue.
Choose planning questions
List the decisions requiring structured data.
Add the field type
Add an appropriate text, date, number or single-select field.
- Worked example: Use Release readiness values Needs evidence, In review and Verified. Keep issue state for open or closed work so completing a planning field does not imply the issue is resolved.
Define values and empties
Define concise values and what empty means.
Populate representative items
Populate representative issues and draft items.
Test the filtered view
Check a filtered view using the field.
Verify the result
A reviewer interprets field values consistently and can locate items missing required planning data.
Common mistakes
Check the handoff edge case
A field with no definition for an empty value makes missing information hard to interpret. Document whether empty means unknown or not applicable.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.