Issue Types Public Preview #148715
Replies: 2 comments 4 replies
-
|
Congrats for the feature release. |
Beta Was this translation helpful? Give feedback.
-
|
It would be nice if the issue types were visible on the list of issues in a milestone (ex: https://github.com/dotnet/android/milestone/38). When looking to prioritize work assigned to a milestone, probably the most important information is whether it is a bug or feature. |
Beta Was this translation helpful? Give feedback.



-
Feedback wanted
Thank you for participating in the issue types public preview. Please leave your feedback below on what is working well, any bugs you encounter, and what else you’d like to see!
To provide your feedback on other experiences released at the same time, please visit:
Issue types
Issues types allow you to classify and manage your issues with a shared and consistent language across all repositories in the organization, such as bugs or tasks.
Customizing default issue types
An organization administrator can customize the issue types that makes sense for the organization from the organization settings "Planning" page in the “Issue types” section, with bug, task, and feature provided by default to get you started. These are available for all repositories in the organization.
Organization settings page
Adding a type to an issue
When you create a new issue, you can change the issue type using the
Typesection on the right. You can also change the issue type from this location once an issue has been created.Screen.Recording.2024-09-30.at.1.45.49.PM.mov
When creating a sub-issue from an issue, you'll find this at the bottom next to the other issue metadata.
Additionally, you can specify the
typequalifier in issue forms in your repositories, so that each issue created from each template automatically has the type set.Issue form with `type` field
If you’d like to add or change the issue type for existing issues, you can update it from the repository page by selecting one or multiple issues using the checkbox to the left of each issue, or from a project using the
Typefield by copying and pasting or dragging cells.Creating custom views in your project
In a project, you can use the new
Typefield to customize your views by filtering, sorting, slicing, or grouping, so you can visualize and understand the breakdown of your issues.You can even use the
Typefield in the auto-add to project workflow, so you can automatically add these to your project.Auto-add to project workflow
Automating issue types
There are now
typedanduntypedwebhook payload objects for the issues webhook event that trigger a GitHub action.For the GraphQL API, there is an IssueType object to manage issue types at the organization level to create, update, and delete them. You can also create a new issue with an issue type, update the issue type, and query a repository by issue type.
Click to view GraphQL details
Note that these requests will need to include the GraphQL-Features header with a value of
issue_types.Objects and Fields
Query Issue.IssueType
Returns issue type based on issue ID
Query IssueType
Returns fields for issue type i.e. private, enabled etc.
Query IssueType.issues connection (w/ repository argument)
Returns total count of issues (with associated fields i.e. title, state etc) with an issue type based on specified repo.
Query issueTypes using global search filter API
Org wide searches for issue type.
Mutations
Create Issue Type
Update Issue Type
Delete Issue Type
Create Issue -> w/ Issue Type
Update Issue -> w/ Issue Type
Update Issue Issue Type
Next steps
We are continuing to improve the Issues experience, and so we’d love to hear your feedback as you try out the new experience and start using issue types.
Beta Was this translation helpful? Give feedback.
All reactions