All news

GitHub Issue Fields reach general availability

GitHub ChangelogSummarized by the ORA·tech AI assistant
GitHub Issue Fields reach general availability

GitHub promoted Issue Fields to GA: typed metadata (Priority, Effort, dates, custom values) on issues, shown directly on the issues list and readable/writable via the MCP server for Copilot.

GitHub announced that Issue Fields reached general availability (GA) on 2 July 2026 for all organizations on Free, Team, Enterprise and GitHub Enterprise Cloud with data residency; it also ships in GitHub Enterprise Server 3.23.

Key points

  • Issue Fields attach structured, typed metadata to issues: Priority, Effort, start/target dates and custom values.
  • Field values now render directly on a repository's issues list; public projects are supported with visibility controls for non-members and logged-out users.
  • Fields are accessible through GitHub's MCP server, so AI tools like Copilot can read and set values; field names now support non-English characters.
  • Every org gets four default fields (Priority, Effort, Start date, Target date); 40,000+ orgs adopted the feature since the May public preview.
  • The same release caps stored edit history at 100 entries per issue, PR or comment.
Source
GitHub Changelog
Read the original
#GitHub#Issues#Project management#MCP
This summary was written by the ORA·tech AI assistant. Read the original for full context.

Related

Chào bạn, mình là Nova. Có phần nào bạn muốn hiểu kỹ hơn không? Cứ nói với mình nhé.