Comment by locknitpicker

> Great post. This should be the default configuration, community can make discussions, contributors can make issues.

I'm not so sure. I think this sort of discussion mostly falls within the realm of bike shedding. I'll explain why.

There's such a thing as a ticket life cycle. Ticketing flows typically feature a triage/reproduction stage. Just because someone creates an issue that doesn't necessarily mean the issue exists or isn't already tracked somewhere else, or that the ticket has all the necessary and sufficient information to troubleshoot an issue. When a ticket is created, the first step is to have someone look at it and check if there's something to it. This happens even when tickets are created by internal stakeholders, such as QAs.

GitHub supports ticket labels, and the default set already cover these scenarios.

https://docs.github.com/en/issues/using-labels-and-milestone...

To me this discussion sounds like a project decided to update their workflow to move triage out of tickets and into a separate board. That's fine, it's the exact same thing but with a slightly more complex process. But it's the same thing.