Issue Forms: Allow control of vertical space and field grouping/formatting in output issue

[jyasskin]

Select Topic Area

Product Feedback

Feature Area

Issues

Body

We recently converted the @w3ctag's design review intake to use issue forms, and we had trouble keeping the new issues vertically-compact and skimmable. Old issues look like w3ctag/design-reviews#1042, with many single-line "fields" in the form

• Field title: value

A naive conversion to issue-forms produces output like jyasskin/test-design-reviews#7, where every field has its own header and section, and it's hard to see how fields are grouped.

We wound up settling on output like w3ctag/design-reviews#1120, where we're using the issue forms just for the most important fields, and to create grouping headers, but the content under those grouping headers still lives in a textarea:

  - type: textarea
    attributes:
      label: Where and by whom is the work is being done?
      value: |
        - GitHub repo:
        - Primary contacts:
          - $name (@-mention), $organization/s, $role in developing feature
          - <!-- repeat as necessary, we recommend including group chairs and editors in this list -->
        - Organization/project driving the design:
        ...

It would be nice to take advantage of the more-structured input and help text that forms provide, but tell the output to live in a bulleted list, or in sub-sections.

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