Do not set default value for required dropdowns in issue templates

[esimkowitz]

Select Topic Area

Bug

Feature Area

Issues

Body

The new issue templates are awesome, but we've noticed that dropdowns are auto-populating with the first value, even if they're listed as required. This is counterintuitive as it means that if the user does nothing, the value will still be populated, possibly with incorrect data. I think that default values are useful, but should be opt-in for template writers to avoid confusion with end users. For required fields, a warning should be provided if a user fails to select an option.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[mr-manuel]

I have the same issue. If I add a dropdown field to an issue template, a value is already preselected. This means, that the required: true flag is useless, since there is always a selection from the beginning. I tried also to set an empty value as default, but that do not work.
My problem is, that I need the required: true flag to work and make sure the dropdown is not preselected in order that the user has to make a selection.
https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

  - type: dropdown
    id: version
    attributes:
      label: Version
      description: What version of our software are you running?
      options:
        - 1.0.2 (Default)
        - 1.0.3 (Edge)
      default: 0
    validations:
      required: true

Reproduction Steps

• Create an issue template
• Add a dropdown field with required: true
• Compile the issue template and do not make any selection
• Hit Create

You will get no This field is required message.

[Aokromes]

totally agree, auto filling mandatory dropdown fields defeats the reason of exist, for example filling incorrect download source or branch.
also, a great adittion to it can be sort of scripting, ie if to old version is filling tell them to update.