Maintenance: Improve issue templates

[shilman]

Issue: N/A

What I did

• Add a question template
• Add labels to issues based on template
• Prompt users for repro repo in bug report
• Add link to discord

Rationale:

• Moving towards a model where bug repros are required by default (with an official repro template TBD)
• Move away from github discussions, which don't support labels
• Prepare for a distributed triage process

How to test

N/A

[tooppaaa]

Any chance we can can ask the framework to the user ? I don't have idea how though :)

[yannbf]

In the System section below we ask users to run npx sb@next info, which will output the @storybook/<framework> package installed and that helps to know the framework, but I'm not sure if you're asking this or you mean asking users to add an issue label like app:<framework> 🤔

[gaetanmaisse]

If we want the label to be automatically set based on the issue's description we can create a simple GitHub Action that will "parse" the System section to find out the SB framework (and version) used and set labels accordingly. But it would not be very relevant in cases of bugs in an addon 🤔

[gaetanmaisse]

If we want the label to be automatically set based on the issue's description we can create a simple GitHub Action that will "parse" the System section to find out the SB framework (and version) used and set labels accordingly. But it would not be very relevant in cases of bugs in an addon 🤔

[domyen]

This is pretty open-ended, which can end up being yield issues that are noisy/generic that we'd then have to close.

If the idea here is to point out areas to improve documentation, perhaps we change the template name to "Request documentation".

If the questions are in fact generic "how to", I'd suggest we use Stack Overflow or Discord instead of creating a GH issue.

[shilman]

I agree that request documentation is more specific. I'll update it to steer people in that direction.

Regarding actual questions, I don't want to introduce yet another system that needs to be triaged. Discord is fine because we already support it. However, my impression is that those answers are very temporal and are pretty much lost into the ether after a day or so. Stack overflow is kind of exactly what we want, but we're setting up a triage process for Github and I'm hoping that having everything in one place will make it easier to route issues to the right place using labels/teams (setting this up with @zol). We've considered Github discussions as a Discord alternative, but unfortunately they don't support labels, so we're going to shut them down.