Support GitHub Issue Fields (structured issue metadata)

[MariusStorhaug]

Summary

GitHub has released Issue Fields — structured, typed metadata at the organization level — into public preview for all organizations (GitHub.com and GitHub Enterprise Cloud).

Reference: Issue fields are now in public preview for all organizations

What are Issue Fields?

Issue fields allow organizations to define typed metadata (e.g., Priority, Effort, or any custom field) at the org level. These fields automatically appear on every issue, in every repository within the org.

Supported field types:

• Single select
• Text
• Number
• Date

Key capabilities:

• Pin fields to specific issue types
• Search and filter issues by field value
• Add fields as columns in project views
• Track changes in the issue timeline
• Automate via REST and GraphQL APIs or webhook events
• Visibility controls: orgs can decide which fields are visible to non-members

Config location: Settings > Planning > Issue fields

Every organization automatically gets four default fields out of the box.

What to support

• Explore using Issue Fields in the PSModule org to replace or supplement labels for structured metadata (e.g., priority, effort)
• Consider automating field values via GitHub Actions workflows using the REST/GraphQL API
• Review whether the Copilot migration skill can help bulk-migrate existing label values to fields

References

• GitHub Changelog – May 21, 2026
• Issue fields documentation
• Community discussion
• Initial preview announcement – March 12, 2026

[MariusStorhaug]

REST API Reference

Docs: REST API endpoints for issue fields

---

Org-level field management

Requires "Issue Fields" organization permission. Classic tokens need read:org (read) or admin:org (write/delete).

Method	Endpoint	Description
GET	/orgs/{org}/issue-fields	List all issue fields for the org
POST	/orgs/{org}/issue-fields	Create a new issue field
PATCH	/orgs/{org}/issue-fields/{issue_field_id}	Update an existing issue field
DELETE	/orgs/{org}/issue-fields/{issue_field_id}	Delete an issue field

Create / Update body parameters:

Parameter	Type	Description
name	string (required on create)	Name of the field
description	string | null	Optional description
data_type	text | date | single_select | number	Field type (required on create)
visibility	organization_members_only | all	Who can see the field (default: organization_members_only)
options	array of objects	Required for single_select; each option has name, description, color

---

Setting field values on issues

Field values are set via the standard Issues endpoints using the issue_field_values body parameter.

Docs: REST API endpoints for issues

Method	Endpoint	Notes
POST	/repos/{owner}/{repo}/issues	Create issue with field values
PATCH	/repos/{owner}/{repo}/issues/{issue_number}	Update field values on an existing issue

issue_field_values parameter (array of objects): each entry must include the field ID and the value to set. Silently dropped if issue fields are not enabled or the user lacks push access.

---

Filtering issues by field value

GET /repos/{owner}/{repo}/issues accepts the query parameter:

issue_field_values=priority:Urgent,effort:High

Format: field_slug:value (comma-separated for multiple fields; all conditions must match — AND logic).

---

Required permissions summary

Operation	Fine-grained permission	Classic scope
Read fields	"Issue Fields" org read	read:org
Create / update / delete fields	"Issue Fields" org write	admin:org
Set field values on issues	"Issues" repo write	repo
Read issues (with field values)	"Issues" repo read	public_repo / repo