Redesign -- New Issue: Bug Report

[kaimmej]

Problem

I think we could have better user experience when they people go to add an issue for our project. This could be simple things such as text areas, instead of raw markdown, drop-down menus for what component of the website it buggy, or simple things, like an emoji in title -> 🐛 Bug report

think it is a cleaner experience for users, and might make for higher quality submissions from people.

I suggest that there are efficiency improvements as well

• we could automatically assign the 'website-Update-Project' to new bug requests. These will still get the untriaged label, and so will still need to be seen, and prioritized, but it takes one step out of the process for our maintainers. Additionaly, it seems like feature requests, and bug reports only go to the website-update-project.
• Validator "required=true" on the fields that we think deserve it.

Example

OpenSearch new bug issue is a good example of what

Solution

Specific changes

• An emoji in the Name of the issue (🐛 Bug report)
• default assign the 'website update project'
• text areas for user-entry, instead of free form user-entry
• dropdown menu for the website component that is affected.

Note

These changes will not affect how the issue is rendered to us, it only affects the issue-intake, and makes it more user friendly.
See these three recent [BUG] reports from OpenSearch, and notice how there are no dropdowns or text-areas being rendered, it looks normal.

• [BUG] GET {index}/_settings does not list number_of_routing_shards as setting OpenSearch#14199
• [BUG] Arrays of geo_shape are broken after v2.8.0 OpenSearch#14193
• [BUG] org.opensearch.cache.common.tier.TieredSpilloverCacheStatsIT.testStatsMatchOldApi is flaky OpenSearch#14169

[nateynateynate]

Closed with #2993