GitHub Issue Fields Generally Available, Edit History Limited
GitHub Issue Fields are now generally available across all plans, offering structured, typed metadata for better issue tracking. Key enhancements since preview include issue list integration, public project support, and MCP integration for AI tools. Additionally, GitHub is now limiting stored edit history for issues and pull requests to 100 entries to align with usage patterns. These changes impact all GitHub users, with some features shipping in Enterprise Server 3.23.
- →Issue fields reach general availability
- →Issue fields enhance issue list visibility and public project support
- →MCP integration enables AI tool access to issue fields
- →Resolved issues with issue field updates and display
- →Edit history for issues and pull requests limited to 100 entries
Features (1) ›
- Issue fields reach general availability
Issue fields, which add structured, typed metadata to issues for tracking priority, effort, and dates, are now generally available for all GitHub organizations. This feature provides searchable, reportable, and consistent metadata across repositories.
Enhancements (3) ›
- Issue fields enhance issue list visibility and public project support
Issue fields now appear directly on the repository issues list for at-a-glance scanning. The feature also supports public projects with configurable visibility controls and allows logged-out users to see public fields.
- MCP integration enables AI tool access to issue fields
Issue fields are now accessible via GitHub's MCP server, allowing AI tools like Copilot to read and set field values when creating or updating issues. Field names also support non-English characters for internationalization.
- Edit history for issues and pull requests limited to 100 entries
GitHub now enforces a limit of 100 stored edits per content item for issues and pull requests. Older edits beyond this limit are automatically removed, preserving the original content and the 99 most recent changes.
Fixes (1) ›
- Resolved issues with issue field updates and display
Several bugs have been fixed, including issues with field updates not reflecting in issue timestamps, project view sorting not updating correctly, fields not appearing in exclusion autocomplete, and single-select options displaying out of order with colors.
Notes (1) ›
- Issue fields available across plans, Enterprise Server 3.23
Issue fields are available for Free, Team, Enterprise, and GitHub Enterprise Cloud organizations and will ship in GitHub Enterprise Server 3.23. The edit history limit also applies to all plans and will ship in GitHub Enterprise Server 3.23.
https://github.blog/changelog/2026-07-02-issue-fields-are-now-generally-available