GitHub Org-Wide Issue Fields Now in Public Preview

GitHub's new Issue Fields feature is now in public preview for all organizations, allowing for structured metadata on issues. This is a big step up from older, less organized tracking methods.
By Newsroom | Software Development, Technology |

GitHub has extended its 'Issue Fields' feature into public preview, allowing all organizations on GitHub.com and GitHub Enterprise Cloud with data residency capabilities to implement structured, organization-level metadata for their issues. This move aims to replace less organized methods, such as label-heavy workarounds, with a more defined system for tracking project details. The preview, announced on May 21, 2026, has already seen adoption by over 1,000 organizations, including major enterprises and open-source projects.

Customizable Metadata Now Available

Organization administrators can now configure these new fields directly within their settings, navigating to 'Settings > Planning > Issue fields'. This enables them to create custom fields, define their data types (like 'Priority' or 'Effort'), and control which fields appear on different types of issues across all repositories within the organization. Previously, this functionality was only available in a limited preview.

Read More: Git-annex removes AI code to ensure software safety

Technical and Usage Details

According to GitHub's documentation, Issue Fields are currently restricted to issues and do not extend to pull requests. The system supports up to 25 fields per organization. Users can manage these fields by navigating to an individual issue to edit or clear existing field values. For programmatic access, the 'Organization issue fields REST API' and 'Issue field values REST API' are available.

Background and Context

The introduction of organization-wide issue fields signifies GitHub's ongoing effort to provide more robust project management tools. This expansion follows a period of initial preview since March, indicating a gradual rollout and refinement of the feature based on early user feedback. The development appears to be part of a broader trend in software development platforms to offer more structured data management for collaborative workflows. Recent release notes from platforms like Releasebot and releases.sh, though not directly detailing issue fields, point to a general industry push towards enhanced tracking and reporting mechanisms, including for AI-related usage metrics.

Read More: Consulting Firms Hire AI Experts in Houston and Dearborn

Frequently Asked Questions

Q: What is GitHub's new 'Issue Fields' feature?
GitHub's 'Issue Fields' feature is now in public preview. It lets organizations add specific details, like priority or effort, to their issues in a structured way. This helps track projects better than before.
Q: Who can use the new GitHub Issue Fields?
All organizations on GitHub.com and GitHub Enterprise Cloud can use this feature. It is available for organizations with data residency capabilities.
Q: How do I set up Issue Fields for my organization?
Organization administrators can set up Issue Fields in their settings. Go to 'Settings > Planning > Issue fields' to create custom fields and choose which ones to use for different issues.
Q: What are the limits for GitHub Issue Fields?
Each organization can have up to 25 custom fields. This feature currently works for issues, not for pull requests.
Q: When did GitHub announce the public preview for Issue Fields?
GitHub announced the public preview for its organization-wide Issue Fields on May 21, 2026. The feature has been in a limited preview since March 2026.