Issue templates are a bit noisy

[krobelus]

Looking at issues like #4838, I'm not sure if blank_issues_enabled: false is very useful, I need to scroll down to see the actual bug report;
if we trust people who know what they are doing to opt out of it, that would reduce noise.
Or at least we could put the obvious questions ("is it still reproducible?") in HTML comments. (For the record, the gh issue create CLI allows creating blank issues regardless).

[zyv]

I do have a strong opinion on this one.

I'm really sick of reading badly structured reports over the decades, and the new templates, however verbose, are at least making it halfway bearable to me. Yes, one can leave some fields empty, and/or put something useless in there, but on the whole it gives a rather rigid structure that you can scan and quickly identify pieces of information you need. Especially with the amount of new reports coming in the last few months, I just wouldn't be able to cope otherwise. And no, I'd only trust people who know how to opt out of this (which is indeed possible as you correctly mentioned, and not only via the CLI, but also with the web interface) to make raw reports that are any better than the default verbose template...

I guess, again, this is influenced by the abysmal quality of the reports I've been dealing with over the decades. Your experience might be completely different, and you'd be rather on the side of being annoyed to be pushed into the overly verbose and rigid structure. I can absolutely understand this, but everyone is looking after their own survival in the end. And however you see it, I'm not at risk of running out of issues in the tracker anytime soon (or even in my lifetime).