GitHub Community
Issue fields: Structured issue metadata is in public preview #189141
Replies: 128 comments 194 replies
-
|
We use issue-only repositories internally to track tasks and manage everything through GitHub Projects. A single repository can have issues for multiple platforms and teams. This feature would help us streamline our workflow, so I'd like to request it be enabled for the @wavera org. |
Beta Was this translation helpful? Give feedback.
-
|
Enabled for |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
We use labels to track over 500 issues for our innovation lab, would be great to get access to the preview @frickegroup |
Beta Was this translation helpful? Give feedback.
-
|
Enabled for |
Beta Was this translation helpful? Give feedback.
-
|
@labudis quick initial feedback. So far it looks quite promising, however sometimes we do add pull requests to our projects board and give them a priority. In the past it worked with project priority field, but there doesn't seem any option to set the new global priority field on pull requests. do you have any idea or insight? |
Beta Was this translation helpful? Give feedback.
-
|
For now Issue fields are an Issues feature so you will not be able to apply Issue fields to PRs but we are monitoring requests for PR support so your feedback is noted! |
Beta Was this translation helpful? Give feedback.
-
|
@labudis and @alexanderniebuhr
|
Beta Was this translation helpful? Give feedback.
-
|
Would like to explore storing Backlog.md's tasks directly as Github issues. This new feature would drastically simplify the integration |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the interest! Issue fields are an organization-level feature, so they need to be enabled on a GitHub organization (not a personal account). Do you have an organization where you'd like us to enable it? |
Beta Was this translation helpful? Give feedback.
-
|
Currently at @arma-events we use fields in projects and issue type, but the integration of issues and projects always lacked a bit imo. Atm we move all isses to a single project to allow setting some metadata like size, status etc. Would love to try out the more issue-centered approach. Also: Is there any change of multi select coming as a field type? I always missed that in projects and the only reason why we still use good all labels for some things (for example affected components) 😕 |
Beta Was this translation helpful? Give feedback.
-
|
Enabled for |
Beta Was this translation helpful? Give feedback.
-
|
+1 for I'd like to migrate from custom labels to Issue Fields for |
Beta Was this translation helpful? Give feedback.
-
|
+1 for |
Beta Was this translation helpful? Give feedback.
-
|
It would be really nice if these and other fields (like type, milestone etc.) could be marked as required at the time of issue creation. |
Beta Was this translation helpful? Give feedback.
-
|
Required fields are on our horizon! Can you share a bit more about your use case? Understanding which fields you'd want to enforce and in what scenarios would be really helpful. |
Beta Was this translation helpful? Give feedback.
-
|
This looks great! Can we get it for the |
Beta Was this translation helpful? Give feedback.
-
|
Access has been enabled for |
Beta Was this translation helpful? Give feedback.
-
|
We'd love to try these! Org is |
Beta Was this translation helpful? Give feedback.
-
|
Access has been enabled for |
Beta Was this translation helpful? Give feedback.
-
|
Hi @pedro-vbai! Just a heads up, we also just shipped visibility settings so issue fields now work on public repositories too. Organization admins can choose which fields are visible publicly and which stay internal. Details here. |
Beta Was this translation helpful? Give feedback.
-
|
These look like great additions! We'd love to try them out @cisagov. We have some fields (priority, effort) in Project metadata that really make more sense on the issue. Structured issue metadata is likely the nudge we'd need to start actually using Issue types. |
Beta Was this translation helpful? Give feedback.
-
|
Access has been enabled for |
Beta Was this translation helpful? Give feedback.
-
|
🎉 Congrats, @labudis! You've done a fantastic job moving this forward and collecting such thorough feedback. Are y'all still thinking that you'll be opening these to public repos by next week? We're in a bit of a holding pattern since migrating from Zenhub and are very eager to get our product ops reporting up and running again. |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
Access has been enabled for |
Beta Was this translation helpful? Give feedback.
-
|
Great news, @amenity! Issue fields now work on public repositories. Organization admins can control which fields are visible to everyone and which are restricted to organization members. Details in this comment. No more holding pattern! |
Beta Was this translation helpful? Give feedback.
-
|
We’d love to request access for the @code0-tech organization. We are currently in the process of building our community and want to ensure a structured workflow from the start. Moving away from label-based workarounds to typed, org-wide metadata like Priority and Effort would be a huge help in streamlining our issue management and reporting. |
Beta Was this translation helpful? Give feedback.
-
|
Amazing, thank you very much 🔥 |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
Access has been enabled for |
Beta Was this translation helpful? Give feedback.
-
|
As the PM for the |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the interest! I wasn't able to find an organization matching |
Beta Was this translation helpful? Give feedback.
-
|
@labudis Sorry, had a typo in there, it's agrc |
Beta Was this translation helpful? Give feedback.
-
|
@labudis Just bumping up this request for |
Beta Was this translation helpful? Give feedback.
-
|
thanks, I added this to be enabled tomorrow! |
Beta Was this translation helpful? Give feedback.
-
|
Access enabled for agrc! Priority and effort fields are now live across your repos. Enjoy! |
Beta Was this translation helpful? Give feedback.
-
|
I personally do not understand why these are bound to an organization and not per repo. In an organization with many different repos the need for different issue fields can be very big. Please make this bound to repos and not organizations! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback! We chose the org-level approach because one of the biggest pain points we heard was inconsistency: every repo ends up with slightly different definitions of "priority" or "effort," making cross-repo reporting and triage really difficult. Could you share more about your use case? Specifically, what makes it difficult to have a single set of fields across your organization? That context would be really helpful as we think about how the feature evolves. |
Beta Was this translation helpful? Give feedback.
-
|
It's not having a single set of fields across my organization that's difficult. It's more that certain repositories have specific needs. For example I am a contributor and close collaborator in the Microsoft PowerToys project. This is an app that consists of many different modules and it would be useful to have an issue field "Module" where we can specify the module. But as this feature is only available on organization level (Microsoft) such a field will (very likely) not be introduced as it is of zero use for other repos. Maybe a hybrid approach where both is possible could be an option? |
Beta Was this translation helpful? Give feedback.
-
|
Same need for large organizations like |
Beta Was this translation helpful? Give feedback.
-
|
Completely agree with @noraa-junker, we also need this for the same reason. |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
Would love to try this for |
Beta Was this translation helpful? Give feedback.
-
|
Ah, we must have missed that in the original announcement - I didn't realise it would only work for private repos for now. Out of interest, why the split between public/private repo support? |
Beta Was this translation helpful? Give feedback.
-
|
Access has been enabled for |
Beta Was this translation helpful? Give feedback.
-
|
Hey @setchy! Issue fields now work on public repositories. Your organization admin can control which fields are visible publicly and which stay internal. Details here. You should be unblocked now! |
Beta Was this translation helpful? Give feedback.
-
|
Awesome, thanks @labudis. Is there plans on the roadmap to support filtering repository Issue Lists using the Issue Fields? ie: show me all 
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, this is on our radar. In the meantime you can filter by typing "Priority" in your search bar and picking "High" from the dropdown. |
Beta Was this translation helpful? Give feedback.
-
|
This looks great! Would love to use it with |
Beta Was this translation helpful? Give feedback.
-
|
@labudis It's been a day and I missed the part about an explanation. Right now I have a lot of labels that start with Priority::, Type::, Status::, Area::, etc., and being able to use this would be a much better way for us to organize those instead of using an absolute ton of labels. |
Beta Was this translation helpful? Give feedback.
-
|
Access has been enabled for |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ViewFromTheBox! Just shipped public repo support for issue fields. You can now use them on public repositories with visibility controls. More info here. |
Beta Was this translation helpful? Give feedback.
-
|
Please enable them for |
Beta Was this translation helpful? Give feedback.
-
|
Enabled for |
Beta Was this translation helpful? Give feedback.
-
|
Could you please enable the issue fields for sds-lab-dev? Thank you for your support. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @superkkt ! You should now have access to issue fields for Docs: Managing issue fields |
Beta Was this translation helpful? Give feedback.
-
|
Hello, Can you enable this on the enterprise level? https://github.com/enterprises/ptcp If not, can you please enable for these orgs? https://github.com/PTCP-Data-Engineering |
Beta Was this translation helpful? Give feedback.
-
|
Hi @nparikh3 ! We've enabled access to issue fields for the 4 organizations you specified. Check your org settings under Organization > Planning > Issue Fields to get started. Let us know how you get on! Docs: Managing issue fields |
Beta Was this translation helpful? Give feedback.
-
|
I am not sure if this has been said, but when trying to set issue field on using the api, the It would be great if we can just use the |
Beta Was this translation helpful? Give feedback.
-
|
Actually, the inconsistency goes even further that the List issue field values for an issue api endpoint expects a |
Beta Was this translation helpful? Give feedback.
-
|
Hey @andyof8feets thank you so much for this feedback and for flagging this inconsistency. I've opened an issue to discuss this |
Beta Was this translation helpful? Give feedback.
-
|
Can we add this to PRs? |
Beta Was this translation helpful? Give feedback.
-
|
At the moment this is only available for Issues but we're monitoring feedback re PR support and I've noted your request there. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Hello! I think I've found a fairly bad bug. When I edit an issue field for an issue (in this case a Priority single select field), it doesn't seem to count as an update for when I then query issues for updated:@today or similar. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @pedro-vbai , thanks for the feedback! I can confirm I'm get the same behaviour, I'll raise this with the team |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I would like to request access for the @BeaniumMC organization, as we have many repositories with issue tracking in multiple projects. It would be great to have some structured standardization across the organization :) |
Beta Was this translation helpful? Give feedback.
-
|
Hi @BigVirusBoi! You should now have access to issue fields for Docs: Managing issue fields |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much! :) |
Beta Was this translation helpful? Give feedback.
-
|
We would like to try out the issue fields in dontenwill-standard |
Beta Was this translation helpful? Give feedback.
-
|
Hi @JulianFuchsDontenwill! We've just enabled issue fields for Docs: Managing issue fields |
Beta Was this translation helpful? Give feedback.
-
|
Are these fields settable through issue templates, similar to |
Beta Was this translation helpful? Give feedback.
-
|
Hi @d-costa at this moment in time they're not unfortunately. But these sorts of use-cases for forms and templates are definitely on our radar. I've made a note of your request, thank you for the feedback! |
Beta Was this translation helpful? Give feedback.
-
|
Integrating it with the other system should have a high prio because that generates so much more value |
Beta Was this translation helpful? Give feedback.
-
|
Organization: We would like to request access to Issue Fields for our organization. Use case: We use a GitHub App (bot) to create and manage issues automatically. Since GitHub Apps cannot be set as issue assignees, we need a custom "Manager" field (single select) to track who is responsible for each issue — whether it is a human member or our bot agent. Issue Fields would solve this limitation cleanly. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Hey @makocchi777 . You should now have access to issue fields on Docs: Managing issue fields |
Beta Was this translation helpful? Give feedback.
-
|
Can we enable this for pewresearch thanks |
Beta Was this translation helpful? Give feedback.
-
|
Hey @sethrubenstein. We've just enabled issue fields for Docs: Managing issue fields |
Beta Was this translation helpful? Give feedback.
-
|
Organization: catenax-eV We would like to request access to Issue Fields for our organization. Thx |
Beta Was this translation helpful? Give feedback.
-
|
Hey @stephanbcbauer. You should now have access to issue fields on Docs: Managing issue fields |
Beta Was this translation helpful? Give feedback.
-
Cool thx. is visible ... we will play a little bit :) |
Beta Was this translation helpful? Give feedback.
-
To support scrum/sprint planing, there is another option needed, something like either |
Beta Was this translation helpful? Give feedback.
-
|
Hi @phifuh, thank you so much for this feedback! Different data types are something on our radar. I've taken a note of your request for an iteration field and your ideas around how you'd want to interact with it. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! |
Beta Was this translation helpful? Give feedback.
-
|
Hey @SkynetTechnology. You should now have access to issue fields on Docs: Managing issue fields |
Beta Was this translation helpful? Give feedback.
-
|
In @ohmyzsh we use custom fields to track issues and work across plugins and themes. Having this baked into the metadata of the issue will be a big improvement in terms of filtering and ergonomics. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hey @mcornella. You should now have access to issue fields on Docs: Managing issue fields |
Beta Was this translation helpful? Give feedback.
-
|
We're actively looking to migrate to GitHub from AZ Devops in https://github.com/organizations/PremierCrop - having custom issue fields would be a huge help! |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
issue.fields.public.preview.mp4
If you've ever used labels like
priority/p0,severity/high, orteam/frontendto track structured data in issues, you know the pain: no types, no validation, no consistency across repositories, and no way to report on them. Issue fields fix all of that. Define typed, org-wide fields once and they show up on every issue, in every repository, automatically. Search by them, report on them, automate with them.Issue fields are now in public preview. We're rolling out access gradually to select organizations. Not all organizations will have access immediately. If you'd like to be enabled sooner, request access in this discussion (see below).
We've been running a private preview since November 2025 and have been iterating based on feedback. Here's what teams are saying:
📦 What you get out of the box
When issue fields are enabled for your organization, you get a ready-to-use setup.
Default fields
Every organization starts with four fields:
Pinned to the right issue types by default
Create a bug and you'll see
PriorityandEffortright there in the sidebar. Create a feature and you get all four. No setup, no config, just works.🔧 Make it your own
The defaults are a starting point. Organization admins can customize everything.
Add new fields
You can add up to 25 fields per organization. Four field types to choose from:
Pin fields to issue types
Decide which fields show up for each type. Pin severity to bugs, impact to features, your custom types, or whatever combination works for your team. You can also pin fields to issues that don't have a type.
Customize options and colors
Rename fields, add descriptions, create and reorder options, pick colors. Changes apply across the entire org instantly.
Control visibility on public repos
Issue fields work on public repositories. Set each field to Public (visible to everyone) or Organization only (visible to org members and collaborators only). All fields default to Organization only, so nothing is exposed unless you choose. Learn more.
🔍 Search by field values
Some things you can do:
📊 Works with Projects
Add any issue field as a column in your project views, then group, filter, and slice by field values. Unlike project custom fields, issue fields travel with the issue across projects and views, so your data stays consistent everywhere.
Issue fields count toward the 50-field limit per project.
📝 Timeline tracking
Every field change shows up in the issue timeline with what changed, when, and who did it.
⚡ API and automation
Full REST API and GraphQL API support for both field settings (create, update, delete fields) and field values (get, set, clear values on issues). Automate field management, do bulk updates, filter by fields, and sync with external tools.
Webhook events (
field_added,field_removed) let you trigger GitHub Actions on field changes:✨ What's new since private preview
Since the private preview, we've fixed over 50 bugs and shipped several improvements:
🔄 Migration tool
Already using labels or project fields for structured data? We built a Copilot skill to help you migrate. It bulk-copies values from labels or project fields into your new org-level issue fields.
🙋 How to request access
Want to try it? Post a comment in this discussion with your organization slug and a brief description of how you'd use it. We'll get back to you.
💬 Feedback
We'd love to hear from you! Share feedback, report issues, or suggest ideas in this discussion. Your input directly shapes what we build next.
To learn more, check out the issue fields documentation.
Beta Was this translation helpful? Give feedback.
All reactions