Dynamic GitHub Issue template creation

[Sparsh0212]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Issues

Body

Hi Team,

Does GitHub support dynamic form selection in input fields for custom github issue template.

[apfisher6-bit]

i think im having the same issue

[v-ember]

Hey @Sparsh0212 ! 👋

Thanks for posting in the GitHub Community! You are more likely to get a useful response if you are posting your question in the applicable category. The Accessibility category is a place for our community to discuss and provide feedback on the digital accessibility of GitHub products. Digital accessibility means that GitHub tools, and technologies, are designed and developed so that people with disabilities can use them.

I've gone ahead and moved this to the correct category for you. Good luck!

[syedahmedx3]

💡 The Verdict: GitHub Issue Forms are Static (Plus Workarounds)

No, GitHub Issue Forms do not support dynamic field selection or conditional rendering based on previous selections. The YAML schema configuration for issue forms is purely static. You cannot change available dropdown values or reveal new inputs dynamically based on what a user selects.

However, depending on your workflow requirements, there are standard architecture patterns to work around this limitation.

---

🛠️ Developer Workarounds

1. The Multi-Template / Chooser Approach (Native UI)

Instead of a single multi-step form, split the logic into multiple dedicated templates and use a chooser configuration file to guide the user.

• Create specific templates under .github/ISSUE_TEMPLATE/bug-frontend.yml and .github/ISSUE_TEMPLATE/bug-backend.yml.
• Use a .github/ISSUE_TEMPLATE/config.yml file to handle routing with an option matrix.

2. Organization-Level "Issue Fields" (New Feature)

GitHub recently rolled out Issue Fields in public preview.

• If you are running an Organization account, admins can navigate to Settings > Planning > Issue fields to define typed, queryable metadata schemas (single-select, text, number, date) at the organization level.
• You can pin these specialized schema blocks to custom Issue Types. While it won't change the form inputs during creation, it forces clean, typed sidebar properties once the issue type is picked.

3. Post-Submit Automation via GitHub Actions (IssueOps)

If you need automated processing based on form fields, turn it into an IssueOps workflow:

1. Define a drop-down or checkbox list statically in your YAML.
2. Use the issue-ops/parser or stefanbuck/github-issue-parser GitHub Action within a workflow triggered by issues.opened.
3. The runner reads the markdown payload, converts it into an easily accessible JSON object, and dynamically assigns labels, adds comments, or opens a linked sub-issue based on the selected criteria.