Skip to content

Add support for issue types in gh cli #9696

Closed

Description

@beingminimal

Describe the feature or problem you’d like to solve

A clear and concise description of what the feature or problem is.

Currently issue types are not supported in gh cli

Proposed solution

How will it benefit CLI and its users?

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.

Activity

  1. jtmcg commented on Oct 3, 2024

    @jtmcg
    Contributor

    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.

  2. added
    gh-issuerelating to the gh issue command
    coreThis issue is not accepting PRs from outside contributors
    and removed on Oct 3, 2024
  3. boronine commented on Mar 29, 2025

    @boronine

    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/

  4. asnare commented on Oct 8, 2025

    @asnare

    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
  5. Lyonk71 commented on Dec 4, 2025

    @Lyonk71

    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:

    • 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).
    • Resolution: Update IssueMetadataState logic (pkg/cmd/pr/shared/params.go).
    • Display: Add 'Type' column to list table and view metadata (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.

  6. BagToad commented on Apr 8, 2026

    @BagToad
    Member

    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!

  7. edburns commented on Jun 13, 2026

    @edburns

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    coreThis issue is not accepting PRs from outside contributorsenhancementa request to improve CLIgh-issuerelating to the gh issue commandneeds-designAn engineering task needs design to proceed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions