Similar experience here, only with an addition from the other side: I'm subscribed to some issues, and get seriously irritated by the number of people who barge in with “This is a show-stopper for our company! We're not migrating from ProductX until this is fixed! Surely it would take just a bit of time to fix this!!!” Very often, such attitude is displayed on feature requests that barely qualify above ‘cosmetic.’ Even on software for programmers like Intellij Idea or Node.js, people whip out the ‘it's an easy job’ argument, or post endless ‘me too’s while failing to comprehend differences in their use-cases.

I see quite a few projects that get steady development, but have hundreds of open issues, of which most are probably feature requests. In my experience, having the tracker flooded with thoughts for features that it would be nice to have someday, is completely useless and probably actively toxic. Ideas are cheap, while implementers' time is finite. Ideas are best dumped into an ‘inbox’ list―most of them will never surface from there anyway.

As a result, I almost completely stopped posting issues, except for most egregious bugs or when a feature would be a one-line change. As a rule, I now prefer posting pull requests, which of course is a lot harder―but helps keeping things in perspective.

This is a problem with expectations. If we treat a bug report as a gift, then the only thing we should expect is that the recipient says "thank you", not that they will ever use it.

But, somehow both sides end up treating it as a work request, and that causes bad feelings.

Before I decide to use an open source library, I check bug reports and see attitude of the library maintainer before I use it. If there is a lot of WONTFIX or arrogant attitude, I simple stay away from such a library.