[deepbluev7]

If I have more problems reported every day than I can fix, the only productive way is to work on issues that people actually put time into reporting in a nice and well worded manner. Because usually only those people give feedback if something is fixed to their liking, stick around for long enough to actually test the fix and are reasonable enough to understand limitations or discuss alternative solutions.

If the only issue my application ever had was reported in such a rude manner, there might be a case to be made to fix it, even though it was reported in a hostile or rude manner. It might make the application better for people who didn't report the issue. But maybe it is more valuable to just spend that time on something fun or enjoyable like coding on something else or eating cake. There is no reason to waste your free time on rude people, when they have the option to just be nice and save you all the anger.

[teddyh]

I don’t see why the attitude of the reporting user should be a factor in determining the priority of the bug they are reporting. Surely the severity of the bug, and how many people are likely to be affected are the relevant factors. Sure, if the issue is not well explained, hard to pin down, or might otherwise require cooperation from the user, you have to weigh that into your consideration. However, many users do get surprisingly cooperative once you show them that you actually care about fixing the issue they are reporting; many users are used to being ignored, and might start out having a bad attitude merely by habit.