You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To manage issues and some automation on top of gh cli this feature needs to be supported.
Additional context
As per this github blog this is going to be released soon so this needs to be supported.
Reacted by Alex Cyphus, Macadamiaouu, Fabian Geisler, Gerjan Stokkink, Yury V. Zaytsev, Gwenn Le Bihan, wilson-cao-volvocars, Robert Weide, hburn7, YAMADA Tsuyoshi and 39 more
We are aware that there is a gap in the CLI tool around Issue Types. It is on our radar but support likely won't be added for some time due to some more pressing needs.
Reacted by Bhaumin, Josh Haines, John Bates, Mark Han and Tom Harrison
As a workaround, to set the issue type on an issue you can make the API call directly:
gh api -X PATCH repos/{owner}/{repo}/issues/1234 --field type=Bug
Reacted by Moulick Aggarwal
Reacted by chrisammon3000, Brian Lalonde, Scott Dunlop, Prayag Savsani, yghgjklh-dotcom, Gwenn Le Bihan, Steve Freudenthaler, Igor Sirotin, Jems and jpep01
I just looked at the codebase, and it looks like adding issue types wouldn’t require new architectural patterns; just plumbing a new field through existing structures:
API (Read/Write): Extend RepoMetadata for available types, update IssueCreate/IssueList queries, and add issueType to exportable fields (api/queries_repo.go, api/queries_issue.go, api/query_builder.go).
Commands: Add --type flag for create/edit, and --type filter for list (pkg/cmd/issue/create/create.go, edit.go, list/list.go).
Issue type support is in progress, covering --type on create/list, --set-type/--remove-type on edit, issueType in --json output, and an interactive type picker. The full design is up for review at #13120. If you have feedback on the proposed flags or behavior, please comment there!
Reacted by Gwenn Le Bihan, Michael Andersen, hburn7, jpep01 and Michał Lüth
Thank you so much for adding this. I have long believed that AzDO Boards type system was far superior for enterprise customers, but I am glad to see type support getting better in GitHub Projects and Issues.
Activity
jtmcg commentedon Oct 3, 2024
Hey @beingminimal, thanks for opening this issue!
We are aware that there is a gap in the CLI tool around Issue Types. It is on our radar but support likely won't be added for some time due to some more pressing needs.
boronine commentedon Mar 29, 2025
If anyone is waiting for this in order to automate label -> issue types migration, you can do this already using the recently released REST API support: https://www.boronine.com/2025/03/29/Migrating-to-GitHub-Issue-Types/
asnare commentedon Oct 8, 2025
As a workaround, to set the issue type on an issue you can make the API call directly:
gh api -X PATCH repos/{owner}/{repo}/issues/1234 --field type=Buggh issues createshould allow setting "type" #12110 as a duplicate of this issueLyonk71 commentedon Dec 4, 2025
Hey @jtmcg,
I just looked at the codebase, and it looks like adding issue types wouldn’t require new architectural patterns; just plumbing a new field through existing structures:
RepoMetadatafor available types, updateIssueCreate/IssueListqueries, and addissueTypeto exportable fields (api/queries_repo.go,api/queries_issue.go,api/query_builder.go).--typeflag for create/edit, and--typefilter for list (pkg/cmd/issue/create/create.go,edit.go,list/list.go).IssueMetadataStatelogic (pkg/cmd/pr/shared/params.go).pkg/cmd/issue/shared/display.go,pkg/cmd/issue/view/view.go).Hope this helps with triaging, since it actually looks quite straightforward... just touches a few different parts of the codebase.
BagToad commentedon Apr 8, 2026
Issue type support is in progress, covering
--typeon create/list,--set-type/--remove-typeon edit,issueTypein--jsonoutput, and an interactive type picker. The full design is up for review at #13120. If you have feedback on the proposed flags or behavior, please comment there!Remove nonexistent --type flag from filing-issues skill
Remove nonexistent --type flag from filing-issues skill
edburns commentedon Jun 13, 2026
Thank you so much for adding this. I have long believed that AzDO Boards type system was far superior for enterprise customers, but I am glad to see type support getting better in GitHub Projects and Issues.