💬 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. ⭐

I tried creating a couple of issue tickets, and both were automatically closed by the bot for not following the prescribed templates — even though I used the template provided.

The only way I could get it to work was by creating the ticket through the web version.

If issue templates are required and automated checks are closing tickets that don’t match them, the mobile app should support those same templates natively. Otherwise, users on mobile can’t reliably see or follow the required format, which makes issue creation frustrating and confusing.

Expected behavior
The Android app should fully support repository issue templates so users can create valid issues directly from mobile without being rejected by the bot.

Why this matters
The app should not let users start an issue flow that is likely to be auto-closed
Templates need to be visible and usable on mobile if they are required for submissions
This would make issue reporting much more consistent across web and mobile
Suggestion
Please add native support for:

selecting issue templates
rendering the full template form in the app
validating required fields before submission
matching the web issue creation experience more closely