Issue fields are now in public preview for all organizations
Source: GitHub Changelog
Overview
Issue fields are now available in public preview to all GitHub organizations on github.com and GitHub Enterprise Cloud with data residency. When you define typed metadata like Priority, Effort, or any custom field at the org level, it automatically appears on every issue in every repository.
Fields support four types (single select, text, number, and date), can be pinned to specific issue types, and work across the platform. You can:
- Search and filter issues by field value
- Add fields as columns in project views
- Track changes in the timeline
- Automate via REST and GraphQL APIs or webhook events
Adoption
Since the initial preview in March, over 1,000 organizations have adopted issue fields, including large enterprises and open‑source projects. Teams are integrating fields into creation workflows and using bots, GitHub Actions, and integrations to keep field values consistent without manual effort.
Common Themes from Early Adopters
- Replacing sprawling label systems with structured, queryable metadata, unifying priority and effort tracking across hundreds of repositories without manual syncing.
- Providing automation with a consistent schema to build on.
Teams describe issue fields as the missing link between issues and projects.
Recent Improvements
- Public repository visibility controls – Organizations can decide which fields are visible to non‑members.
- REST API parity – Set field values when creating issues via the REST API, matching existing GraphQL support.
- Migration tool – A Copilot skill that bulk copies values from labels or project fields.
Default Fields
Every organization automatically receives four default fields that work out of the box. Organization admins can customize fields, add new ones, and configure which fields appear on each issue type from Settings > Planning > Issue fields.
Learn More
- Documentation: Managing issue fields in an organization
- Community discussion: