[quote:1js2senf]The bug report guidelines are there to help you too! They exist because bug reports that don't follow them are generally completely useless, and we cannot do anything to help you. People very often do things like report a bug which is nothing but a screenshot of an error message.
Already having expressed my disappointment in how bugs reports are handled. I do however understand that you would like a Capx to test out things when bugs are reported.
However regardless of them adding a capx, the impression you get when bug reports are handled, is that its more a matter of getting them closed than looking into the report it self.
Just because a bug is closed or a bug report is not filled out as you would like them, doesn't mean that it have been solved. Its of great frustration to put together a bug report trying to highlight and explain exactly how and what is going on. To just see it being moved to the closed section as if that would solve it. In a lot of cases (speaking for my self), if the way to recreate the problem is to do 3-4 steps which takes less than a minute to do. Why should the bug report be closed? Even when a screenshot is applied showing that the capx doesn't contain anything other than a single event.
In other cases bugs are not as simple as they can be or would make sense if reported on there own, because they depend on each other. But again these are just moved to closed bugs section, because the bugs shouldn't be like that. Only one bug per report.
But if some actions lead to something else which causes the bug, and you as user don't know where things go wrong, you report it as you have experienced it. And if you during you test notice other things, then it makes perfect sense to report that as well, because how should you as user know whether that is relevant for the bug or not? But to you it might seem like a different issue, which I don't blame you for, but that doesn't mean that I know it and that I intentionally try to add as many bugs to one report as humanly possible, to just make things as complicated for you as possible.
The whole workflow of you just closing bug reports, could be compared to two people speaking on the phone.
Person 1: Expresses a problem
Person 2: I don't agree, its because you are not doing it correctly.
Person 1: But......(Person 2 hangs up.)
I think the general way that you handle bug reports are very ineffective. Instead of just closing them, it would be a lot better approach I think. To add a system of how you handle them, in the sense:
1. If you don't understand the problem / can recreate it.
Don't assume that the problem is solved by moving it to the closed section.
2. Write a reply to the person:
a. Based on your description in the report, Im not able to recreate the problem. Can you apply a Capx?, if there is none
b. I checked you capx and weren't able to recreate the issue you are referring to. <Ask for more information if possible>
c. I don't understand your description (Not all people speak English), can you try to elaborate the problem?
Don't close the reports as if it was solved or not relevant. Instead maybe wait 4-7 days and if the person making the report haven't answers to your comment then close it. People making these reports, simply write what they experience, not specifically where in the C2 code things are going wrong.
If you under no circumstances can recreate the problem, leave the bug report open to see if others might report something similar and write that you simply can't recreate it, but you will keep an eye on it and the person making it should as well or close it, but at least tell the person that you cant recreate it, after gathering as much information as possible. Following the 3 steps above.
And I fully agree that in a lot of cases I would also assume that some bug reports are due to bad code, but in that case simply ask them to provide a capx, if the problem or description in the bug report doesn't explain how to recreate it correctly or it is a more advance description etc. People adding bug reports doesn't do it to annoy you, but to help you. But the impression you get is that you would rather that people didn't based on the way you do it now, and that's sad I think