Github supports having multiple issue template types, which might make the issue opener's experience better.
I thought that having separate templates for bugs, features, and questions might be useful.
Perhaps we should set this up?

See https://blog.github.com/2018-05-02-issue-template-improvements/
cc @PikBot
I am not a particularly big fan of that, for two reasons: (a) we have like 20 repos where this would apply, so unless this can be defined at the org level there's a lot of overhead, and (b) I think our existing template is already pretty good in guiding the user to provide relevant information. When we triage the tickets we can tag them as "enhancement" or "question" or "bug", which probably will be more accurate than having the user unfamiliar with the project to make that choice.
I don't think there is a way to define this at organization level, it would have to be done separately for each repo. Also, I think it would be much faster if project maintainers did it, because then it is just a matter of two clicks (contributors don't have access the repo's settings, it would have to be done manually).
Here is a collection of issue templates that might be helpful:
https://github.com/stevemao/github-issue-templates
Most helpful comment
I don't think there is a way to define this at organization level, it would have to be done separately for each repo. Also, I think it would be much faster if project maintainers did it, because then it is just a matter of two clicks (contributors don't have access the repo's settings, it would have to be done manually).
Here is a collection of issue templates that might be helpful:
https://github.com/stevemao/github-issue-templates