M U Let me present the other side of this:
We're already dealing with way more reported issues than we can handle. Issues that aren't actually actionable, or are incomplete, just end up wasting time we could spend more productively elsewhere. For example, I've spent probably several weeks of full time work over 3 years trying to track down issues that were fixed and released by the time a bug was filed against an older version of Jenkins.
Therefore we added, in bold red letters, with red border, below the 'Summary' field when creating a new issue:
Please read our JIRA guidelines before creating an issue.
The first sentence, a "notice" on the linked wiki page, on yellow "note" background, with "warning" symbol next to it:
The Jenkins JIRA is not a support site. If you need assistance or have general questions, visit us in chat, or email one of the mailing lists.
This is followed by quite detailed instructions what to do before filing a bug, and what information to provide.
So don't be surprised then if issues that look like requests for help, and don't provide crucial information, receive negative responses.
And to clarify – it's not like we're not reading IRC or the mailing lists either and just want you to go away; the three people responding to you here are among the most active users there!