UX can help a bit, but fundamentally the problem is people who have an issue or question but are completely unable to communicate it in a way that can be understood and addressed.

The garbage bug reports I see on my projects and others are like, either one sentence or rambling nonsense. The templates don't help much, these users will do their best to ignore them.

As long as you're not doing that, your bug report is probably very welcome.

UX is partly about how to accommodate that without throwing up hoops to jump through to the people who aren't a waste of space.

Most bug reports, especially on complex software should follow something resembling a kind of wizard/state machine (e.g. state: OS has/has not been specified) but instead everything is a text box with a dump of contextual questions, half of which don't even necessarily make sense for the specific bug report you're making.

>As long as you're not doing that, your bug report is probably very welcome.

When barriers are thrown up to the other kind of person it will often make it seem like they are very unwelcome even when they're not - e.g. the first message you see may be a hostile list of "DON'T DO THESE 5 THINGS" because somebody once did each of those things. I'm pretty sure a lot of good bug reports are lost this way.