GitHub Issue Forms Disappearing? A Key `name` Field Length Fix for Software Development Management

The Mystery of Missing GitHub Issue Forms Unraveled

Developers often rely on GitHub's issue forms to streamline bug reporting, feature requests, and task management. These structured templates are crucial for maintaining consistent data and efficient software development management. However, a recent community discussion highlighted a perplexing issue: valid issue templates disappearing from the chooser, hindering effective workflow management.

The Problem Unveiled: Templates Not Displaying

Mikoshiba-Kyu initiated a discussion after noticing that despite having multiple YAML issue forms correctly placed under .github/ISSUE_TEMPLATE, only one template was visible in the GitHub GUI. Other templates were simply not appearing, making them unusable for issue creation.

Key observations from the original post included:

• Multiple YAML issue forms existed in the correct directory.
• Only one template was shown, others were missing.
• The issue appeared in both company and personal repositories, suggesting a broader problem.
• Renaming files seemed to coincide with the issue, but reverting names didn't fix it.
• Templates that had existed for a while continued to appear, while recently added or renamed ones were more likely to be missing.

The repository structure typically looked like this:

.github/ISSUE_TEMPLATE/
 bug.yml
 feature.yml
 task.yml

Mikoshiba-Kyu confirmed all standard checks: files in the right place, committed to the default branch, issues enabled, labels existing, UTF-8 encoding with LF line endings, and no obvious YAML syntax problems. This pointed strongly to a GitHub-side issue with re-indexing or re-recognition of issue forms.

Community Confirmation and the Breakthrough

Another user, Donnerstagnacht, echoed similar frustrations, noting that their custom templates were missing while unexpected 'default' templates appeared instead. This further solidified the suspicion of a platform-wide glitch rather than isolated configuration errors, impacting efficient software development management practices.

The breakthrough came when Mikoshiba-Kyu identified the root cause and a simple workaround: issue form templates are not recognized if the name field within the YAML file is shorter than 3 characters.

For instance:

• A template with name: バグ (2 characters in Japanese) was not showing up. Renaming it to name: バグチケット (longer name) fixed the issue immediately.
• The same behavior was confirmed in English: name: B or name: Bu failed, while name: Bug (3 characters) worked perfectly.

This critical detail was undocumented, and the GitHub UI provided no error or warning, making diagnosis incredibly frustrating for developers.

Impact and Recommendation for Workflow Optimization

This undocumented restriction can severely disrupt issue creation workflows, a critical component of software development management. If you're experiencing missing GitHub issue templates, the first step is to immediately check the length of the name field in your YAML files.

Ensuring your template names are at least three characters long can instantly resolve this frustrating visibility issue, restoring your structured issue creation process and improving overall developer productivity. This insight underscores the importance of community collaboration in uncovering undocumented behaviors in developer tools, which can significantly impact the efficiency of software development management.