gh issue create issue type supports old behavior

Whether due to permission errors or not (#13804), this has resulted in unexpected behavior:

-Open • A4-Tacks (A4-Tacks)
+Enhancement · Open • A4-Tacks (A4-Tacks)

Current:

? Issue type  [Use arrows to move, type to filter]
> Enhancement
  Feature Request
  Bug

Expect like:

? Issue type  [Use arrows to move, type to filter]
> [None]
  Enhancement
  Feature Request
  Bug

Thanks for the report! This looks like an enhancement request rather than a regression: the interactive "Issue type" prompt added in

cli/pkg/cmd/issue/create/create.go

Lines 362 to 378 in 0d121e8

    
           // Interactive issue type selection 
        
           if opts.IssueType == "" { 
        
           	issueTypes, typesErr := api.RepoIssueTypes(apiClient, baseRepo) 
        
           	if typesErr == nil && len(issueTypes) > 0 { 
        
           		typeNames := make([]string, len(issueTypes)) 
        
           		for i, t := range issueTypes { 
        
           			typeNames[i] = t.Name 
        
           		} 
        
           		var selected int 
        
           		selected, err = opts.Prompter.Select("Issue type", "", typeNames) 
        
           		if err != nil { 
        
           			return 
        
           		} 
        
           		opts.IssueType = typeNames[selected] 
        
           		opts.issueTypeID = issueTypes[selected].ID 
        
           	} 
        
           }

always builds its option list directly from the repo's configured issue types and never inserts a "none selected" choice, so there's currently no way to skip setting a type interactively. I'm suggesting enhancement and gh-issue. This isn't a duplicate of #13804/#14367 (those are about the permission error thrown when applying the selected type), since this issue is specifically about the prompt lacking a "none" option.

Generated by Issue Triage (skills-driven) for #14386 · copilot · auto · 35.4 AIC · ⌖ 2.01 AIC · ⊞ 11.2K · ◷

@A4-Tacks

Hey @A4-Tacks, is your issue here that you are being forced to choose an issue type when you don't want to?

Yes, usually, I don't want a issue type

(Issues created using templates on the web also seem to have no issue type)

@BagToad

Yeh fair enough @BagToad you did the work here, are we missing something in being able to avoid selecting a type?

@williammartin

@williammartin I think this is just an oversight. We should have a way to say you don't want a type interactively.

There's some related work going on in #13899 that I haven't had a chance to review again.

We should have a way to say you don't want a type interactively.

Using config/option seems to bring a lot of trouble. Is there any harm in adding a [None] item?

12. > We should have a way to say you don't want a type interactively.
     Using config/option seems to bring a lot of trouble. Is there any harm in adding a `[None]` item?

Sorry for the confusion - I didn't mean to suggest a config option. I think your suggestion to add some None value to the options is the correction one 👍

I find this change also surprising: specifically the web allows me to create an issue without a "type" but the cli forces me to choose one.

What I expect is different from the OP: I'd expect the selection of "type" to move to the same place "labels" are i.e under optional metadata to add once the issue is created.

I do not think it's worth creating a different issue to describe this but I'm happy to if it makes things more clear.

@cli/code-reviewers I’d like to contribute a small fix here: add (none) as the first issue-type choice, leave the type unset when selected, and preserve selection of real types. The wording would match the milestone picker.

Would this scope be welcome as an external contribution? If so, could you confirm the acceptance criteria and add help wanted?

I have a local fix with regression coverage. I noticed #14448 was closed unmerged, so I wanted to check before opening another PR.

Sunbelt Computer Software

PL/B Language Development and Support

Navigation Menu

Repository navigation

`gh issue create` issue type supports old behavior #14386

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	// Interactive issue type selection
	if opts.IssueType == "" {
	issueTypes, typesErr := api.RepoIssueTypes(apiClient, baseRepo)
	if typesErr == nil && len(issueTypes) > 0 {
	typeNames := make([]string, len(issueTypes))
	for i, t := range issueTypes {
	typeNames[i] = t.Name
	}
	var selected int
	selected, err = opts.Prompter.Select("Issue type", "", typeNames)
	if err != nil {
	return
	}
	opts.IssueType = typeNames[selected]
	opts.issueTypeID = issueTypes[selected].ID
	}
	}

Sunbelt Computer Software

PL/B Language Development and Support

gh issue create issue type supports old behavior #14386

Description

Activity

cli-triage commented on Sep 8, 2026

williammartin commented on Sep 10, 2026

A4-Tacks commented on Sep 10, 2026

williammartin commented on Sep 10, 2026

BagToad commented on Sep 10, 2026

A4-Tacks commented on Sep 10, 2026

BagToad commented on Sep 10, 2026

pokui commented on Oct 3, 2026

yousefissa commented on Oct 4, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`gh issue create` issue type supports old behavior #14386