GitHub Community
Issue fields: Structured issue metadata is in public preview #189141
Replies: 361 comments 555 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.
-
|
@rodneyjoyce you should now have access, could you please confirm? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, thank you - it is working very well |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Estoy tratando de todavía implementar espérenme el paso . 🙏🏻 |
Beta Was this translation helpful? Give feedback.
-
|
Good luck |
Beta Was this translation helpful? Give feedback.
-
|
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 chance of multi select coming as a field type? I always missed that in projects and the only reason why we still use good old labels for some things (for example affected components) 😕 |
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.
-
|
+1 for multi-select. Has there been any progress with this? We'd like to use this for platforms as well. |
Beta Was this translation helpful? Give feedback.
-
|
+1 for |
Beta Was this translation helpful? Give feedback.
-
|
+1 (as if y'all don't know 🙈) for multi-select. We're also going to continue using |
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.
-
|
@labudis Sorry for my extremely late answer. Generally, we want to make fields required to ensure integrity across issues. For example, issues opened by product management should have a minimum set of fields they must fill in. As an example, in our project we link every issue to a milestone, and there shouldn't be any issue without a milestone. Required fields would ensure this. |
Beta Was this translation helpful? Give feedback.
-
|
Required fields would be excellent for the exact same reason as @kutsan articulated previously. It's honestly something that, migrating over 6 months ago from Azure DevOps, I thought would already be natively present here. |
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.
-
|
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.
-
|
When reading this i thought about the 2 most upvoted feature requests inside the repo discussion: https://github.com/orgs/community/discussions/4174 Grouping repos could work very well with "global" issue fields |
Beta Was this translation helpful? Give feedback.
-
|
We also have a few repo-specific fields, such as the module field, which we currently track using labels. It would be useful for us to support both global and repo-specific fields. A setup similar to GitHub Actions secrets could work well, where values can be defined at the organization level or per repository. |
Beta Was this translation helpful? Give feedback.
-
|
Would love to try this for |
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.
-
|
@labudis any forecast as to when those would appear in the UI so we don't have to manually type it? I love this new feature, it would be great to drop custom labels in favor of built-in fields, lack of UI is hindering. |
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.
-
|
I think that this is a good feature, especially timeline tracking since we have issues with process level observability with project fields. However the flow we want to observe the most happens on PRs so it's a bit of a nonstarter on our end. Voicing support for extending this to PRs as well |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback. PR support is something we've heard from several people and it's on our radar. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Very cool thing |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
I think this is an awesome feature! I like that we get full customizability on a project level as well. We currently work on a project with iterations, is there any way to use the fields start date, end date or even an iteration to automatically asign an iteration to it? |
Beta Was this translation helpful? Give feedback.
-
|
The default values for Priority and Effort overlap so it's not immediately obvious which value belongs to which field. 
|
Beta Was this translation helpful? Give feedback.
-
|
renaming single-select options breaks projects that use the field, esp. when using the field as columns or swimlanes (board views) or groups (table view): for columns, it creates new columns for the new option names but leaves the old columns there, and cards aren't moved to the new columns. But the issues themselves do have the new option names. The same thing happens with swimlanes. in view tables, grouping by the field causes the table to become empty I tried removing the field from the project and re-adding it, to no avail. duplicating a view or making a copy of the project doesnt help either |
Beta Was this translation helpful? Give feedback.
-
|
First off, this is a great feature and I'm already using it extensively! If I could make one request related to the project integration, that would be to have the ability to filter on fields in workflows. For example, I would like to be able to auto-add issues to a project with a certain field value. |
Beta Was this translation helpful? Give feedback.
-
|
can issue fields please be added to pull-requests |
Beta Was this translation helpful? Give feedback.
-
|
I've been trying the numeric field for versions, seems it isn't intended for that, I guess my bad; two thoughts:
currently 5.10 is reduced to 5.1, oops :-) |
Beta Was this translation helpful? Give feedback.
This comment was marked as low quality.
This comment was marked as low quality.
-
|
Hi @Ascalad , thanks for participating! Unfortunately, we don’t currently have moderators for languages other than English. Until that changes, we need to ask that everyone use English here in the GitHub Community when posting to ensure discussions are adhering to our Code of Conduct. |
Beta Was this translation helpful? Give feedback.
-
|
I think this is a great feature addition! One thing that I believe would be useful in some instances is to have the ability to toggle fields (maybe through the gear icon) independently from the issue type as an addition to the default fields. That way, for example, if something is a task but you still want to have the ability to select a target date for completing the task, you can do that. Or, if something doesn't have a type assigned to it but you would like to select more than just priority, that's available as well. |
Beta Was this translation helpful? Give feedback.
-
|
Hallo,yes..wie come again? |
Beta Was this translation helpful? Give feedback.
-
|
It's been great to see this feature rolled out, but we really need a new 
|
Beta Was this translation helpful? Give feedback.
-
|
It used to be:
Now GitHub is slowly turning into Jira. Not very painful while you are following along, but in the end, it will suffer from the same issues as Atlassian and the old Microsoft products – bloated, overly complex, focusing on the wrong thing: the plan, not the planning. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry have noch plan.. |
Beta Was this translation helpful? Give feedback.
-
Where? 😞 
|
Beta Was this translation helpful? Give feedback.
-
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 for all organizations on GitHub.com and GitHub Enterprise Cloud. No invite or waitlist needed. Manage them in your org settings under Settings > Planning > Issue fields. Changelog
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.
Issue fields are fully supported in public and internal Projects. Field visibility settings are respected: only fields set to Public appear in public projects, while Organization only fields are automatically excluded.
📝 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:
https://api.githubcopilot.com/mcp/). Works with any MCP-compatible client. Details🔄 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.
💬 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