Unify Bug Report Templates

[stephanie-anderson]

I noticed all our issue templates for bug reports differ and ask for very different information and levels of details. I will go through all and try to bring the best of all to each of them.

After comparing all web SDK bug report templates, I suggest to:

• always use forms for creating issues (instead of markdown)
• always set the label "Type: Bug" for bug reports
• always ask users where they host (SaaS / on-prem)
• always be specific about the "SDK version" (let's not call it environment etc)
• let users know what to expect after creating an issue (see Java, where we link to the triage process)

See Miro for more details: https://miro.com/app/board/uXjVMBwtrF8=/

Tasks

Beta Give feedback

1. Update bug report template sentry-php#1565
   +0
   
2. Create GH issue templates sentry-laravel#728
   +0
   
3. Create GH issue templates sentry-symfony#744
   +0